From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: pull-request: mac80211-next 2014-03-19
Date: Thu, 20 Mar 2014 11:53:51 -0400 [thread overview]
Message-ID: <20140320155350.GA12987@tuxdriver.com> (raw)
In-Reply-To: <1395261190.4142.34.camel@jlt4.sipsolutions.net>
On Wed, Mar 19, 2014 at 09:33:10PM +0100, Johannes Berg wrote:
> John,
>
> Following your announcement, I figured I should get some code to you
> still, if only because I'm lazy and don't want to disentangle the code I
> already have later to break it up into fixes and features ...
>
> This has a whole bunch of bugfixes for things that went into -next
> previously as well as some other bugfixes I didn't want to rush into
> 3.14 at this point. The rest of it is some cleanups and a few small
> features, the biggest of which is probably Janusz's regulatory DFS CAC
> time code.
>
> Please let me know if there's any problem.
>
> johannes
>
> ---
>
> The following changes since commit 6658ab80fd4ef940fc2366ddb66690a15ea69c18:
>
> mac80211: ibss: handle cfg80211_chandef_dfs_required() error codes (2014-02-21 09:37:46 +0100)
>
> are available in the git repository at:
>
> git://git.kernel.org/pub/scm/linux/kernel/git/jberg/mac80211-next.git for-john
>
> for you to fetch changes up to 73fb08e24ae840bc518facc2c605dd6bb3751fec:
>
> cfg80211: remove macro ASSERT_RDEV_LOCK(rdev) (2014-03-19 21:29:58 +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:[~2014-03-20 16:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-19 20:33 pull-request: mac80211-next 2014-03-19 Johannes Berg
2014-03-20 15:53 ` 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=20140320155350.GA12987@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.