linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: David Miller <davem@davemloft.net>,
	linux-wireless@vger.kernel.org, netdev@vger.kernel.org
Subject: Re: pull request: wireless-next 2014-02-20
Date: Mon, 24 Feb 2014 14:49:33 -0500	[thread overview]
Message-ID: <20140224194932.GE24810@tuxdriver.com> (raw)
In-Reply-To: <53068E22.5050003@lwfinger.net>

On Thu, Feb 20, 2014 at 05:22:10PM -0600, Larry Finger wrote:
> On 02/20/2014 04:29 PM, David Miller wrote:
> >From: "John W. Linville" <linville@tuxdriver.com>
> >Date: Thu, 20 Feb 2014 15:30:05 -0500
> >
> >>Please pull this batch of wireless updates intended for the 3.15
> >>stream!
> >>
> >>For the mac80211 bits, Johannes says:
> >>
> >>"We have some cleanups and minor fixes as well as userspace API
> >>improvements from a lot of people, extended VHT support for radiotap
> >>from Emmanuel, CSA improvements from Andrei, Luca and Michal. I've also
> >>included my work on hwsim to make dynamic registration of radios
> >>possible."
> >>
> >>Along with that, we get the usual round of updates to ath9k,
> >>brcmfmac, mwifiex, wcn36xx, and the ti drivers -- nothing particularly
> >>noteworthy, mostly just random updates and refactoring.
> >>
> >>Also included is a pull of the wireless tree, intended to resolve
> >>some potential merge issues.
> >>
> >>Please let me know if there are problems!
> >
> >Pulled, but please address this:
> >
> >drivers/staging/rtl8821ae/rtl8821ae/trx.c: In function ‘rtl8821ae_rx_query_desc’:
> >drivers/staging/rtl8821ae/rtl8821ae/trx.c:619:3: warning: passing argument 1 of ‘ieee80211_is_robust_mgmt_frame’ from incompatible pointer type [enabled by default]
> >
> >I was going to do the easy transformation to the "_" prefixed variant
> >but noticed that this code doesn't validate the skb length, which is
> >precisely the reason why this routine now takes an skb.
> 
> David,
> 
> That staging driver is expected to be deleted in a commit to be
> submitted in about one week. The new one will be in the regular
> wireless tree. The staging version was submitted so that there would
> be a driver in 3.14.
> 
> I was surprised to see this patch in John's list. It should have
> gone through GregKH. In fact, has has been suppressing all cleanups
> because the better one will be available soon.
> 
> I suggest that you drop this one now. I will, however, check the new
> source to make sure that the skb length is checked.
> 
> Thanks,
> 
> Larry

I'll be reverting that patch in wireless-next -- I goofed by merging
a staging patch in the first place.

John
-- 
John W. Linville		Someday the world will need a hero, and you
linville@tuxdriver.com			might be all we have.  Be ready.

      reply	other threads:[~2014-02-24 20:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-20 20:30 pull request: wireless-next 2014-02-20 John W. Linville
2014-02-20 22:29 ` David Miller
2014-02-20 23:22   ` Larry Finger
2014-02-24 19:49     ` John W. Linville [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=20140224194932.GE24810@tuxdriver.com \
    --to=linville@tuxdriver.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=davem@davemloft.net \
    --cc=linux-wireless@vger.kernel.org \
    --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).