From: Samuel Ortiz <sameo@linux.intel.com>
To: inux-kernel <linux-kernel@vger.kernel.org>,
Greg Kroah-Hartmann <greg@kroah.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Kay Sievers <kay.sievers@vrfy.org>
Subject: [PATCH 0/7 v2] firmware: dynamic firmware id allocation
Date: Wed, 27 May 2009 00:49:30 +0200 [thread overview]
Message-ID: <20090526224930.145059254@linux.intel.com> (raw)
Hi Greg, hi Andrew,
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,6 remove all FIRMWARE_NAME_MAX references from the kernel
code.
Patch #7 gets rid of the FIRMWARE_NAME_MAX definition, and should be applied
only once all previous patches from this patch set are applied.
Cheers,
Samuel.
v2: Included John Linville's patch for the libertas wireless driver.
--
Intel Open Source Technology Centre
http://oss.intel.com/
next reply other threads:[~2009-05-26 22:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-26 22:49 Samuel Ortiz [this message]
2009-05-26 22:49 ` [PATCH 1/7 v2] firmware: allocate firmware id dynamically Samuel Ortiz
2009-05-26 22:49 ` [PATCH 2/7 v2] atm/ueagle-atm: prepare for FIRMWARE_NAME_MAX removal Samuel Ortiz
2009-05-26 22:49 ` [PATCH 3/7 v2] tuners/xc2028: " Samuel Ortiz
2009-05-26 22:49 ` [PATCH 4/7 v2] dvb/dvb-usb: " Samuel Ortiz
2009-05-26 22:49 ` [PATCH 5/7 v2] pcmcia/ds: " Samuel Ortiz
2009-05-26 22:49 ` [PATCH 6/7 v2] wireless/libertas: " Samuel Ortiz
2009-05-26 22:49 ` [PATCH 7/7 v2] firmware: " Samuel Ortiz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090526224930.145059254@linux.intel.com \
--to=sameo@linux.intel.com \
--cc=akpm@linux-foundation.org \
--cc=greg@kroah.com \
--cc=kay.sievers@vrfy.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox