All of lore.kernel.org
 help / color / mirror / Atom feed
From: "John W. Linville" <linville@tuxdriver.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: pull-request: mac80211-next 2013-10-21
Date: Tue, 5 Nov 2013 15:47:34 -0500	[thread overview]
Message-ID: <20131105204733.GC8264@tuxdriver.com> (raw)
In-Reply-To: <1382360937.14310.49.camel@jlt4.sipsolutions.net>

On Mon, Oct 21, 2013 at 03:08:57PM +0200, Johannes Berg wrote:
> Now with build fixes for !MESH and a channel switch parsing fix.
> 
> In this round for mac80211-next I have:
>  * mesh channel switch support
>  * a CCM rewrite, using potential hardware offloads
>  * SMPS for AP mode
>  * RF-kill GPIO driver updates to make it usable as an ACPI driver
>  * regulatory improvements
>  * documentation fixes
>  * DFS for IBSS mode
>  * and a few small other fixes/improvements
> 
> Let me know if there's any problem.
> 
> johannes
> 
> The following changes since commit 7578d57520f51093f590d68e16965e2714e69747:
> 
>   mac80211: implement STA CSA for drivers using channel contexts (2013-10-02 18:18:23 +0200)
> 
> 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 cf867bc30d9af3c2cdbf876224f400a81606eebe:
> 
>   nl80211: fix channel switch parsing (2013-10-21 14:36:56 +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.

      reply	other threads:[~2013-11-05 21:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-21 13:08 pull-request: mac80211-next 2013-10-21 Johannes Berg
2013-11-05 20:47 ` 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=20131105204733.GC8264@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.