| 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
| ||
|
Message-ID: <20090526190415.GA3500@tuxdriver.com> Date: Tue, 26 May 2009 21:04:16 +0200 From: "John W. Linville" <linville@...driver.com> To: Samuel Ortiz <sameo@...ux.intel.com> Cc: linux-kernel <linux-kernel@...r.kernel.org>, Greg Kroah-Hartmann <greg@...ah.com>, Kay Sievers <kay.sievers@...y.org> Subject: Re: [PATCH 0/6] firmware: dynamic firmware id allocation On Tue, May 26, 2009 at 07:40:12PM +0200, Samuel Ortiz wrote: > This 6 patches patch set allows for a removal of the firmware name length > restriction from the firmware class API. > Currently we're limited to 30 characters for firmware names because of a > statically allocated 30 bytes string in the firmware class code. We also want > to remove the FIRMWARE_NAME_MAX definition to prevent future drivers from > referencing it. > > Patch #1 removes that restriction by dynamically allocating the firmware id. > Patches #2,3,4,5 remove all FIRMWARE_NAME_MAX references from the kernel code. > Patch #6 gets rid of the FIRMWARE_NAME_MAX definition, and should be applied > only once all previous patches from this patch set are applied. You probably want to include "libertas: adapt for dynamic firmware id allocation" in this series... :-) John -- John W. Linville Someday the world will need a hero, and you linville@...driver.com might be all we have. Be ready. -- 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/
Powered by blists - more mailing lists