linux-kernel - Re: [PATCH 01/23] byteorder: only use linux/swab.h

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Tue, 06 Jan 2009 14:32:33 -0800
From:	Harvey Harrison <harvey.harrison@...il.com>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	David Miller <davem@...emloft.net>,
	Chris Zankel <chris@...kel.net>,
	Kyle McMartin <kyle@...artin.ca>,
	Jesper Nilsson <jesper.nilsson@...s.com>,
	Gerd Hoffmann <kraxel@...hat.com>,
	bluebird <bluebird@...too.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 01/23] byteorder: only use linux/swab.h

On Tue, 2009-01-06 at 14:08 -0800, Linus Torvalds wrote:
> 
> On Tue, 6 Jan 2009, Harvey Harrison wrote:
> >
> > The first step to make swab.h a regular header that will
> > include an asm/swab.h with arch overrides.
> 
> Btw, was there some reason why you didn't just do the <asm/swab.h> files 
> first? That would seem to simplify the whole sequence, and in fact it 
> would also allow me to just apply all the "create asm/swab.h" patches 
> first regardless of any other work..
> 
> 		Linus


My goal was the elimination of the linux/byteorder.h you objected to while
not breaking the arch overrides of the arches that had already converted.

So it's not just moving to swab.h, it also eliminates the linux/byteorder.h
includes, for this to work, I need to fix swab.h first.

Harvey

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/