From: "Rafał Miłecki" <zajec5@gmail.com>
To: "John W. Linville" <linville@tuxdriver.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 16:36:17 +0200 [thread overview]
Message-ID: <BANLkTimF3Jr4Kp7rDo1dvdBxVPepr__OZw@mail.gmail.com> (raw)
In-Reply-To: <20110604130413.GA3929@tuxdriver.com>
W dniu 4 czerwca 2011 15:04 użytkownik John W. Linville
<linville@tuxdriver.com> napisał:
> 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.
OK, I was just afraid you missed this one :) Sorry if I meant rude.
--
Rafał
prev parent reply other threads:[~2011-06-04 14:36 UTC|newest]
Thread overview: 4+ 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
2011-06-04 14:36 ` Rafał Miłecki [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=BANLkTimF3Jr4Kp7rDo1dvdBxVPepr__OZw@mail.gmail.com \
--to=zajec5@gmail.com \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@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;
as well as URLs for NNTP newsgroup(s).