linux-kernel - Re: [PATCH] firmware: Arrange WHENCE in alphabetical order to avoid conflicts

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:	Sun, 21 Dec 2008 12:12:59 +0000
From:	David Woodhouse <dwmw2@...radead.org>
To:	Jaswinder Singh <jaswinder@...radead.org>
Cc:	Linus Torvalds <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] firmware: Arrange WHENCE in alphabetical order to
 avoid conflicts

On Sun, 2008-12-21 at 17:23 +0530, Jaswinder Singh wrote:
> 
> We are facing problems while we prepare patch for firmware as we add
> new stuff at the end.
> As per David Woodhouse suggestion, I am arranging WHENCE to
> aplhabetical order by driver name to avoid conflicts.
> Thanks to my son Gurchet Singh to help me in arranging driver names in
> alphabetical order.
> 
> Signed-off-by: Jaswinder Singh <jaswinder@...radead.org>

Acked-by: David Woodhouse <David.Woodhouse@...el.com>

Now we're trying to push the remaining conversions to request_firmware()
via the driver authors, putting it into alphabetical order should help
to avoid the conflicts.

If we could have this in before 2.6.28 (since it's purely cosmetic) or
immediately thereafter, that would be great.

Thanks, Jaswinder.

-- 
David Woodhouse                            Open Source Technology Centre
David.Woodhouse@...el.com                              Intel Corporation

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