linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: Samuel Ortiz <samuel.ortiz@intel.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
	"Zhu, Yi" <yi.zhu@intel.com>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 2/3] iwmc3200wifi: shrink calibration lmac name
Date: Tue, 02 Jun 2009 10:02:03 +0200	[thread overview]
Message-ID: <1243929723.3192.44.camel@localhost.localdomain> (raw)
In-Reply-To: <20090602075439.GA4376@sortiz.org>

Hi Samuel,

> > > Firmware names can not be longer than 30 characters, and
> > > iwmc3200wifi-lmac-calib-sdio.bin is too long.
> > > Renaming it to iwmc3200wifi-calib-sdio.bin.
> > > 
> > > Signed-off-by: Samuel Ortiz <samuel.ortiz@intel.com>
> > > Signed-off-by: Zhu Yi <yi.zhu@intel.com>
> > 
> > Is this still wanted?
> I havent heard anything from Greg regarding my firmware name length patch set.
> I'll ping him and check if the patches are queued for rc1 inclusion.
> Meanwhile I think you can leave this one aside for now, thanks.

actually we have to get the firmware straight before 2.6.31-rc1 hits the
streets. So at some point we have to make up our mind ;)

Either way is fine btw. and fixing the firmware name length limitation
is also the right thing to do. Cutting the name because of a bogus
legacy limitation was just the wrong fix here ;)

Regards

Marcel



  reply	other threads:[~2009-06-02  8:02 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-26  3:10 [PATCH 1/3] iwmc3200wifi: fix fragmentation threshold setting Zhu Yi
2009-05-26  3:10 ` [PATCH 2/3] iwmc3200wifi: shrink calibration lmac name Zhu Yi
2009-05-26  3:10   ` [PATCH 3/3] iwmc3200wifi: fix link error when CFG80211 is not selected Zhu Yi
2009-05-26  5:42     ` David Miller
2009-05-26  4:43   ` [PATCH 2/3] iwmc3200wifi: shrink calibration lmac name Marcel Holtmann
2009-05-26  6:02     ` Zhu Yi
2009-05-26  6:33       ` Marcel Holtmann
2009-05-26  6:36         ` Christoph Hellwig
2009-05-26  6:36           ` Zhu Yi
2009-05-26  6:41           ` Marcel Holtmann
2009-05-26  6:47         ` Zhu Yi
2009-05-26  8:51           ` Marcel Holtmann
2009-05-26 11:04             ` Samuel Ortiz
2009-05-26 11:06               ` Kay Sievers
2009-05-26 14:03                 ` Samuel Ortiz
2009-05-26  6:04     ` David Miller
2009-06-01 18:29   ` John W. Linville
2009-06-02  7:52     ` Zhu Yi
2009-06-02  8:09       ` Samuel Ortiz
2009-06-02  7:54     ` Samuel Ortiz
2009-06-02  8:02       ` Marcel Holtmann [this message]
2009-06-02  8:24         ` 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=1243929723.3192.44.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    --cc=samuel.ortiz@intel.com \
    --cc=yi.zhu@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;
as well as URLs for NNTP newsgroup(s).