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-next 2014-07-03
Date: Tue, 08 Jul 2014 14:13:28 -0700 (PDT)	[thread overview]
Message-ID: <20140708.141328.1589777085621867948.davem@davemloft.net> (raw)
In-Reply-To: <20140703204141.GD13303@tuxdriver.com>

From: "John W. Linville" <linville@tuxdriver.com>
Date: Thu, 3 Jul 2014 16:41:42 -0400

> On Thu, Jul 03, 2014 at 03:12:11PM -0400, John W. Linville wrote:
>> Dave,
>> 
>> Please pull this first batch of wireless updates intended for the
>> 3.17 stream...
>> 
>> For the mac80211 bits, Johannes says:
>> 
>> "The biggest thing here is probably Arik's TDLS rework, beyond that we
>> have smaller improvements and features like David's scanning IE thing,
>> Luca's queue work, some CSA work, etc. Also your PID rate control
>> removal, of course."
>> 
>> For the iwlwifi bits, Emmanuel says:
>> 
>> "I have here a fix from Eliad for scheduled scan: it fixes a firmware
>> assertion. Arik reverts a patch I made that didn't take into account
>> that 3160 doesn't have UAPSD and hence, we can't assume that all
>> newer firmwares support the feature. Here too, the visible effect
>> is a firmware assertion. Along with that, we have a few fixes and
>> additions to the device list."
> 
> I copied the wrong text.  It should have read as follows:
> 
> "I have here a whole bunch of various things. Andy contributes
> better debug prints for dvm specific flows and a module parameter to
> completely disable power save for dvm. Andrei is sharing the premises
> of his work on CSA - more to come. Eran and Liad keep on working
> on the new devices. I have the regular amount of BT Coex stuff and
> I continue to work on the firmware error report system adding more
> debug capabilities. More to come on that subject too."
> 
> Sorry for the confusion!

I fixed the text up and pulled, thanks John.

      reply	other threads:[~2014-07-08 21:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-03 19:12 pull request: wireless-next 2014-07-03 John W. Linville
     [not found] ` <20140703191211.GB13303-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>
2014-07-03 20:41   ` John W. Linville
2014-07-08 21:13     ` 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=20140708.141328.1589777085621867948.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).