linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH] cfg80211: advertise possible interface combinations
Date: Fri, 13 May 2011 16:55:02 +0200	[thread overview]
Message-ID: <1305298502.3468.7.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <1305277137.3487.7.camel@jlt3.sipsolutions.net> (sfid-20110513_105908_152174_A8DD220B)

On Fri, 2011-05-13 at 10:58 +0200, Johannes Berg wrote:
> From: Johannes Berg <johannes.berg@intel.com>
> 
> Add the ability to advertise interface combinations in nl80211.

iw code in this branch (until patch is merged, then I'll put the code
into master):

http://git.sipsolutions.net/?p=iw.git;a=shortlog;h=refs/heads/iface-combinations

johannes


      reply	other threads:[~2011-05-13 15:17 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-13  8:58 [PATCH] cfg80211: advertise possible interface combinations Johannes Berg
2011-05-13 14:55 ` Johannes Berg [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=1305298502.3468.7.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=linux-wireless@vger.kernel.org \
    --cc=linville@tuxdriver.com \
    /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).