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-06-14
Date: Fri, 14 Jun 2013 13:32:11 -0400 [thread overview]
Message-ID: <20130614173210.GA28497@tuxdriver.com> (raw)
In-Reply-To: <1371206930.8278.8.camel@jlt4.sipsolutions.net>
On Fri, Jun 14, 2013 at 12:48:50PM +0200, Johannes Berg wrote:
> John,
>
> Here are some more things for -next. I will have another pull request
> some time next week because we're preparing to release the firmware for
> the 7000 series devices, and unfortunately that will require an API
> bump.
>
> This time I have a number of cleanups, a small fix from Emmanuel and two
> performance improvements that combined reduce our driver's CPU
> utilisation as much as 75% in high TX-throughput scenarios.
>
> johannes
>
>
> The following changes since commit 8eb3871076875f247483f4a1fe6713e6d440c53e:
>
> iwlwifi: mvm: Update the supported interface combinations (2013-06-11 20:17:06 +0200)
>
> 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 adaf69186c24100d34c2fb107dacd33546cad3c5:
>
> iwlwifi: mvm: remove obsolete comment (2013-06-13 16:43:16 +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-06-14 17:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 10:48 pull-request: iwlwifi-next 2013-06-14 Johannes Berg
2013-06-14 17:32 ` 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=20130614173210.GA28497@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.