public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Samuel Ortiz <sameo@linux.intel.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
	Greg Kroah-Hartmann <greg@kroah.com>,
	Kay Sievers <kay.sievers@vrfy.org>
Subject: Re: [PATCH 0/6] firmware: dynamic firmware id allocation
Date: Tue, 26 May 2009 21:04:16 +0200	[thread overview]
Message-ID: <20090526190415.GA3500@tuxdriver.com> (raw)
In-Reply-To: <20090526174012.423883376@linux.intel.com>

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@tuxdriver.com			might be all we have.  Be ready.

      parent reply	other threads:[~2009-05-26 19:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-26 17:40 [PATCH 0/6] firmware: dynamic firmware id allocation Samuel Ortiz
2009-05-26 17:40 ` [PATCH 1/6] firmware: allocate firmware id dynamically Samuel Ortiz
2009-05-26 17:40 ` [PATCH 2/6] atm/ueagle-atm: prepare for FIRMWARE_NAME_MAX removal Samuel Ortiz
2009-05-26 17:40 ` [PATCH 3/6] tuners/xc2028: " Samuel Ortiz
2009-05-26 17:40 ` [PATCH 4/6] dvb/dvb-usb: " Samuel Ortiz
2009-05-26 18:32   ` Michael Krufky
2009-05-26 18:42     ` Samuel Ortiz
2009-05-26 18:44       ` Michael Krufky
2009-05-26 17:40 ` [PATCH 5/6] pcmcia/ds: " Samuel Ortiz
2009-05-26 17:40 ` [PATCH 6/6] firmware: " Samuel Ortiz
2009-05-26 19:04 ` John W. Linville [this message]

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=20090526190415.GA3500@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=greg@kroah.com \
    --cc=kay.sievers@vrfy.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sameo@linux.intel.com \
    /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