From: "John W. Linville" <linville@tuxdriver.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: davem@davemloft.net, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org
Subject: Re: pull request: wireless-2.6 2011-06-03
Date: Sat, 4 Jun 2011 09:04:14 -0400 [thread overview]
Message-ID: <20110604130413.GA3929@tuxdriver.com> (raw)
In-Reply-To: <BANLkTimoeVDQK+zu=U+nSM_kj0a3-hh_Jg@mail.gmail.com>
On Fri, Jun 03, 2011 at 11:24:49PM +0200, Rafał Miłecki wrote:
> On Jun 3, 2011 10:03 PM, "John W. Linville" <linville@tuxdriver.com> wrote:
> >
> > Dave,
> >
> > Here is a batch of fixes intended for 3.0 -- I guess I'll need to
> > rename my tree eventually... :-)
> >
> > Included are a libertas fix to ensure proper sequence number assignment
> > on transmitted frames, an ath9k fix that propogates an earlier fix to a
> > few more places, a fix for a cfg80211 regression caused by some mesh
> > code changes, a locking fix for the bluetooth l2cap code, a zd1211rw
> > regression fix, a collection of small fixes for wl12xx, an iwl4965
> > fix for a bad temperature check, an a device ID-related fix for iwlagn.
> >
> > Please let me know if there are problems!
>
> John, you didn't.take my fix for regression in ssb. I really want this for
> 3.0.quickly, as few ppl already had problems with machine locking on boot.
Yours isn't the only fix, and I had quite a few queued already. Patience.
--
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-06-04 13:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-03 19:52 pull request: wireless-2.6 2011-06-03 John W. Linville
2011-06-03 23:53 ` David Miller
[not found] ` <BANLkTimoeVDQK+zu=U+nSM_kj0a3-hh_Jg@mail.gmail.com>
2011-06-04 13:04 ` John W. Linville [this message]
2011-06-04 14:36 ` Rafał Miłecki
2011-06-04 14:36 ` Rafał Miłecki
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=20110604130413.GA3929@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=zajec5@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.