linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: Kalle Valo <kvalo@adurom.com>
Cc: linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [ANN] new wireless stack trees
Date: Wed, 06 Jun 2012 09:03:00 +0200	[thread overview]
Message-ID: <1338966180.4513.4.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <87sje86i1j.fsf@purkki.adurom.net>

On Wed, 2012-06-06 at 10:00 +0300, Kalle Valo wrote:
> Johannes Berg <johannes@sipsolutions.net> writes:
> 
> > Given the amount of work going on in the various wireless stack
> > components, I've decided that I'll reflect my maintainer role also in
> > git trees. I've created new trees and will pick patches for
> >  * mac80211
> >  * cfg80211
> >  * rfkill (if needed)
> >
> > into the new trees
> >  * http://git.kernel.org/?p=linux/kernel/git/jberg/mac80211.git;a=summary
> >  * http://git.kernel.org/?p=linux/kernel/git/jberg/mac80211-next.git;a=summary
> 
> Great!
> 
> > I won't maintain an integration tree like John's wireless-testing,
> > please continue to use his. If merge conflicts make it necessary, I'll
> > resolve them in separate branches etc. and work it out with John.
> 
> So when working on mac80211 or cfg80211 changes you still recommend the
> developer to use wireless-testing, did I understand this correctly?

Most of the time, I probably won't care. You might want to give me hints
as to which tree I should apply the patch to but I'm pretty confident I
can also make that call most of the time :-)

johannes


  reply	other threads:[~2012-06-06  7:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-05 12:11 [ANN] new wireless stack trees Johannes Berg
2012-06-06  7:00 ` Kalle Valo
2012-06-06  7:03   ` Johannes Berg [this message]
2012-06-07  8:59 ` Arend van Spriel
2012-06-09  8:25   ` Johannes Berg

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=1338966180.4513.4.camel@jlt3.sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=kvalo@adurom.com \
    --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).