Messages in this thread | | | Date | Sun, 25 Feb 2007 11:42:33 +0100 | From | Pavel Machek <> | Subject | Re: [PATCH 05/44 take 2] [UBI] internal common header |
| |
On Tue 2007-02-20 15:33:18, David Woodhouse wrote: > On Tue, 2007-02-20 at 10:22 -0500, Theodore Tso wrote: > > But __be32 will catch the same errors these days because the be/le > > types use __bitwise now, right? So use of the __be32/__be64 types should > > be preferred since it also will work with sparse, I would think. > > Does __bitwise work in gcc? I thought it was only for sparse?
Hmm... if you have superior endian-debugging infrastructure, perhaps you should just move rest of kernel to it? Having two endian-debugging infrastructures is ugly... Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html - 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/
| |