From: Johannes Berg <johannes@sipsolutions.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: davem@davemloft.net, linux-wireless@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: pull request: wireless-next 2011-11-28
Date: Tue, 29 Nov 2011 14:54:33 +0100 [thread overview]
Message-ID: <1322574873.4110.15.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <20111129134243.GB2705@tuxdriver.com>
On Tue, 2011-11-29 at 08:42 -0500, John W. Linville wrote:
> > > Johannes Berg (12):
> >
> > > mac80211: use skb list for fragments
> > > mac80211: move fragment flag adjustment
> > > mac80211: make TX LED handling independent of fragmentation
> > > mac80211: transmit fragment list to drivers
> >
> > Since you included these patches, can you please pick up "mac80211: fix
> > TX warning" relatively quickly? It fixes a harmless but possibly
> > recurring WARN_ON in this code.
>
> It's already in wireless-next. :-)
Yeah, sorry, I noticed an hour later or so that I'd been checking the
wrong tree (without updating first)
johannes
prev parent reply other threads:[~2011-11-29 13:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 20:02 pull request: wireless-next 2011-11-28 John W. Linville
[not found] ` <20111128200221.GD2681-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2011-11-29 0:55 ` David Miller
[not found] ` <20111128.195516.37800643865997337.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2011-11-29 11:58 ` Kalle Valo
2011-11-29 8:22 ` Johannes Berg
[not found] ` <1322554972.4110.0.camel-8upI4CBIZJIJvtFkdXX2HixXY32XiHfO@public.gmane.org>
2011-11-29 13:42 ` John W. Linville
2011-11-29 13:54 ` Johannes Berg [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=1322574873.4110.15.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=davem@davemloft.net \
--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).