linux-kernel - Re: [PATCH 00/18] firmware: moving drivers to request

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:	Thu, 05 Jun 2008 18:39:01 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	David Woodhouse <dwmw2@...radead.org>
CC:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/18] firmware: moving drivers to request_firmware()

David Woodhouse wrote:
> On Thu, 2008-06-05 at 18:11 -0400, Jeff Garzik wrote:
>> Thus, if you are going to be touching the in-tree firmwares at all, it 
>> doesn't make sense to convert from C source to any format other than 
>> native binary.
> 
> I disagree. But feel free to post patches which get applied and prove me
> wrong. I'm not going to object if you want to go convert a few more
> drivers.

IMO, if-and-only-if you are touching driver firmwares, you should not do 
anything but render them into their preferred form.

It is useless churn that increases maintenance annoyances to convert an 
in-tree firmware to something other than the form it's in now, so you 
might as well get it right.

	Jeff


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