From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "Guy, Wey-Yi" <wey-yi.w.guy@intel.com>, linux-wireless@vger.kernel.org
Subject: Re: new maintenance release of iwlwifi 1000 uCode available
Date: Wed, 6 Apr 2011 10:27:12 -0400 [thread overview]
Message-ID: <20110406142711.GB11941@tuxdriver.com> (raw)
In-Reply-To: <1302099870.4090.3.camel@jlt3.sipsolutions.net>
On Wed, Apr 06, 2011 at 04:24:30PM +0200, Johannes Berg wrote:
> On Wed, 2011-04-06 at 10:12 -0400, John W. Linville wrote:
> > On Mon, Apr 04, 2011 at 12:34:31PM -0700, Guy, Wey-Yi wrote:
> > > Hi,
> > >
> > > Maintenance release version 39.31.5.1 of uCode for Intel 1000BGN
> > > Series
> > > WiFi Adapter is now available for download from
> > > http://intellinuxwireless.org/?n=Downloads
> > >
> > > Changes:
> > > - Fix "tid mismatch" issue
> > >
> > > Wey-Yi
> >
> > Hmmm...the previous release was 128.50.3.1...
> >
> > I realize that the API portion advanced from 3.1 to 5.1, but the
> > overall release number appears to be moving backwards. Is this
> > intentional?
>
> They're all over the place and basically random ... I *think* they
> depend on the branch it comes from internally, but I'm not even sure.
OK, I can cope. But if you (i.e. your team) can influence them
towards a sane numbering scheme, it will probably make packagers
and/or release engineers happier in the distros...
John
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
next prev parent reply other threads:[~2011-04-06 14:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-04 19:34 new maintenance release of iwlwifi 1000 uCode available Guy, Wey-Yi
2011-04-04 23:38 ` Luis R. Rodriguez
2011-04-05 2:11 ` Guy, Wey-Yi W
2011-04-05 11:06 ` Rafał Miłecki
2011-04-06 14:12 ` John W. Linville
2011-04-06 14:22 ` Guy, Wey-Yi
2011-04-06 14:24 ` Johannes Berg
2011-04-06 14:27 ` John W. Linville [this message]
2011-04-06 14:24 ` Guy, Wey-Yi
2011-04-06 18:49 ` Gábor Stefanik
2011-04-06 18:55 ` Johannes Berg
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=20110406142711.GB11941@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=wey-yi.w.guy@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).