DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:cc:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=xTvBuBVB6FaOzjWtn+1WlvSq4sLzXhmFWO1HRULfAflf4Jl6jJ92HNPpNwyi+HObl4
         /ta8Jm34gw+moe55fhaL7gEDpn3RigezmA1e3Ot3QUmVabjE0s1GQxHXB6W0JPYKriDG
         /+n9Z2qsx0q3vnKCTvzT+V8HQFow1NgGuwaH0=
Message-ID: <8bd0f97a0812290435l12b0eb0ds11c1c56428cfc4a1@mail.gmail.com>
Date: Mon, 29 Dec 2008 07:35:42 -0500
From: "Mike Frysinger" <vapier.adi@gmail.com>
To: walt <w41ter@gmail.com>
Subject: Re: Should <linux/serial.h> define __u32?
Cc: linux-kernel@vger.kernel.org, "Linus Torvalds" <torvalds@osdl.org>
In-Reply-To: <4957FCA4.4010201@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20081010103447.31597.42992.stgit@localhost.localdomain>
	 <20081010103637.31597.41557.stgit@localhost.localdomain>
	 <4957FCA4.4010201@gmail.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 636
Lines: 15

On Sun, Dec 28, 2008 at 17:24, walt <w41ter@gmail.com> wrote:
> So, my question is:  who should be responsible for defining
> that __u32, the author of serial.h or the author of the wine
> code that includes serial.h?

the kernel header should be doing #include <linux/serial.h>

if your distro doesnt patch their current headers to do this, then you
should open a bug report for them
-mike
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/