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]

Message-Id: <1212273914.2534.35.camel@shinybook.infradead.org>
Date:	Sat, 31 May 2008 23:45:14 +0100
From:	David Woodhouse <dwmw2@...radead.org>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 00/18] firmware: moving drivers to request_firmware()

On Thu, 2008-06-05 at 18:39 -0400, Jeff Garzik wrote:
> 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.

I believe that making that change would cause extra controversy that I
don't need, and make it harder for me to get what I _actually_ care
about merged -- which is the basic conversion to request_firmware().

But as I said, if _you_ want to start converting drivers and posting
patches which add raw binary blobs in the firmware/ directory, please
feel free. If they go in without comment, I'll be happy to admit that I
was wrong and start doing raw binaries in future.

-- 
dwmw2

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