linux-kernel - Re: [PATCH] ip2: use 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: <4856C795.2050007@garzik.org>
Date:	Mon, 16 Jun 2008 16:05:41 -0400
From:	Jeff Garzik <jeff@...zik.org>
To:	Alan Cox <alan@...rguk.ukuu.org.uk>
CC:	David Woodhouse <dwmw2@...radead.org>,
	linux-kernel@...r.kernel.org, jaswinder@...radead.org
Subject: Re: [PATCH] ip2: use request_firmware()

Jeff Garzik wrote:
> Except for the part where the firmware is pointlessly separated from the 
> driver.

  ...in the kernel source tree, I mean.

No objection to extracting the firmware from the driver.

Driver maintenance will be more of a pain if we have most of a driver 
<here> in the tree, except for that one crucial piece hiding over <there>.

There is no reason why firmware must be artificially separated into 
firmware/

	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/