From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: pull-request: iwlwifi-next 2013-10-18
Date: Fri, 18 Oct 2013 13:58:35 -0400 [thread overview]
Message-ID: <20131018175835.GE28130@tuxdriver.com> (raw)
In-Reply-To: <1382106086.14393.10.camel@jlt4.sipsolutions.net>
On Fri, Oct 18, 2013 at 04:21:26PM +0200, Johannes Berg wrote:
> John,
>
> And for iwlwifi-next ... This is bigger. I guess -next stuff can wait
> until after KS though. Also, I think there might be a merge conflict
> hidden here, don't really remember.
>
> For this round, I have a lot of changes:
> * power management improvements
> * BT coexistence improvements/updates
> * new device support
> * VHT support
> * IBSS support (though due to a small bug it requires new firmware)
> * various other fixes/improvements.
>
> Sorry to concentrate it all into one pull request, I was holding for a
> small bugfix that turned out to be much more difficult than I expected,
> but also not needed yet (so this code has a known bug with -8 firmware,
> but we'll fix it before the driver gets updated to use that firmware.)
>
> Let me know if there's any problem.
>
> johannes
>
>
> The following changes since commit e25aa82a89db9e3b09d02b5481aa375c7712a10d:
>
> rt2x00: rt2800lib: fix VGC adjustment for RT3572 and RT3593 (2013-10-10 13:53:07 -0400)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-next.git for-john
>
> for you to fetch changes up to 246dd9922e859768aa522daa6c1c601785e57e0c:
>
> iwlwifi: mvm: fix operator precedence (2013-10-18 16:02:38 +0200)
Pulling now...
--
John W. Linville Someday the world will need a hero, and you
linville@tuxdriver.com might be all we have. Be ready.
prev parent reply other threads:[~2013-10-18 18:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-18 14:21 pull-request: iwlwifi-next 2013-10-18 Johannes Berg
2013-10-18 17:58 ` 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=20131018175835.GE28130@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@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).