netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: linville@tuxdriver.com
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: pull request: wireless 2014-03-07
Date: Mon, 10 Mar 2014 14:11:37 -0400 (EDT)	[thread overview]
Message-ID: <20140310.141137.446886429226185509.davem@davemloft.net> (raw)
In-Reply-To: <20140307211239.GC12787@tuxdriver.com>

From: "John W. Linville" <linville@tuxdriver.com>
Date: Fri, 7 Mar 2014 16:12:39 -0500

> Please pull this batch of fixes intende for the 3.14 stream...
> 
> For the mac80211 bits, Johannes says:
> 
> "Here I have a fix from Eliad for the minimal channel width calculation
> in the mac80211 code which lead to monitor mode not working at all for
> drivers using that. One of my fixes is for an issue noticed by Michal,
> we clear an already cleared value but do it without locking, so just
> remove that. The other is for a data leak - we leak two bytes of kernel
> memory out over the air in QoS NULL frames because those don't get a
> sequence number assigned in the TX path."
> 
> For the iwlwifi bits, Emmanuel says:
> 
> "One more fix and an update for device IDs.
> There is a bugzilla reported for the fix which is mentioned in the commit message."
> 
> Along with those...
> 
> Amitkumar Karwar provides two mwifiex fixes, both correcting some
> data transcription problems.
> 
> Ivaylo Dimitrov uses skb_trim in the wl1251 driver to avoid
> HAVE_EFFICIENT_UNALIGNED_ACCESS problems.
> 
> Please let me know if there are problems!

Pulled, thanks John.

But we're getting really late in the -rc at this point, please limit 'net'
pull requests to absolutely the most critical bug fixes from here on out.

Thanks again.

      reply	other threads:[~2014-03-10 18:11 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-07 21:12 pull request: wireless 2014-03-07 John W. Linville
2014-03-10 18:11 ` David Miller [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=20140310.141137.446886429226185509.davem@davemloft.net \
    --to=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).