linux-kernel - Re: [GIT]: Networking

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] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 6 Jan 2009 06:51:44 +0100
From:	Sam Ravnborg <sam@...nborg.org>
To:	Jaswinder Singh Rajput <jaswinderlinux@...il.com>
Cc:	David Miller <davem@...emloft.net>, torvalds@...ux-foundation.org,
	akpm@...ux-foundation.org, netdev@...r.kernel.org,
	LKML <linux-kernel@...r.kernel.org>,
	David Woodhouse <dwmw2@...radead.org>
Subject: Re: [GIT]: Networking

On Tue, Jan 06, 2009 at 10:44:11AM +0530, Jaswinder Singh Rajput wrote:
> On Tue, Jan 6, 2009 at 10:19 AM, David Miller <davem@...emloft.net> wrote:
> >
> > I had 4 firmware patches to apply, each one had to add entries
> > to the same file.
> >
> > The first patch had to be skipped.
> >
> 
> In firmware we maintain WHENCE, so every time we add new firmware we
> also update WHENCE.
> 
> We are facing problems while we prepare patch for firmware as we add
> new stuff at the end.
> As per David Woodhouse suggestion, I arranged WHENCE to alphabetical
> order by driver name to avoid conflicts.
> 
> I also send patch on 21 Dec 2008 with ack of David Woodhouse to linus
> and waiting from his side.
> 
> [PATCH] firmware: Arrange WHENCE in alphabetical order to avoid conflicts
> 
> I think this will resolve very soon, once we update WHENCE in
> alphabetical order, If you better suggestions, please let me know.

We should avoid a central file and push this information
out to the Kconfig files that are at the driver site.

Then we can postprocess autoconf.h to get the filenames etc.

And IMO it is wrong to stroe the firmware files far away
from the driver where they belong.

Sorting WHENCE is a good approach under the current ways
of doing it. But the current ways of doing it looks plain wrong to me.

	Sam
--
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/