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-02-01 (was: pull-request: iwlwifi-next 2013-01-30)
Date: Fri, 1 Feb 2013 14:20:30 -0500 [thread overview]
Message-ID: <20130201192030.GB29418@tuxdriver.com> (raw)
In-Reply-To: <1359715120.8528.11.camel@jlt4.sipsolutions.net>
On Fri, Feb 01, 2013 at 11:38:40AM +0100, Johannes Berg wrote:
> John,
>
> Please excuse my overriding an earlier pull request again. Fengguang
> Wu's build testing found that we had a few symbol conflicts between the
> two subdrivers (iwldvm and the new iwlmvm) so I fixed those. I also
> included a few more patches that we'd worked on and I put in for
> publishing since then.
>
> So what I have here is some cleanups, preparations and the new MVM
> (multi-virtual MAC) driver itself and (this is new) some work on the
> transport API as well as a message flooding fix.
>
> Let me know if there are any problems.
>
> johannes
>
> The following changes since commit c331997b6c9ad7f4b8075e6e60d3caa6e36f5938:
>
> wil6210: fix wil_vring_init_tx status (2013-01-30 15:07:19 -0500)
>
> 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 e56b04efc1f795da42cf1d9651b52a4a5bebd730:
>
> iwlwifi: move register access lock into transport (2013-02-01 11:27:22 +0100)
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-02-01 19:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-30 21:01 pull-request: iwlwifi-next 2013-01-30 Johannes Berg
2013-02-01 10:38 ` pull-request: iwlwifi-next 2013-02-01 (was: pull-request: iwlwifi-next 2013-01-30) Johannes Berg
2013-02-01 19:20 ` 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=20130201192030.GB29418@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).