linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@kernel.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, lkp@intel.com
Subject: Re: [PATCH wireless] MAINTAINERS: add common wireless and wireless-next trees
Date: Sat, 15 Jan 2022 13:11:54 +0200	[thread overview]
Message-ID: <87o84ds16t.fsf@kernel.org> (raw)
In-Reply-To: <20220115081809.64c9fec5@canb.auug.org.au> (Stephen Rothwell's message of "Sat, 15 Jan 2022 08:18:09 +1100")

Stephen Rothwell <sfr@canb.auug.org.au> writes:

> Hi Kalle,
>
> On Fri, 14 Jan 2022 15:34:15 +0200 Kalle Valo <kvalo@kernel.org> wrote:
>>
>> For easier maintenance we have decided to create common wireless and
>> wireless-next trees for all wireless patches. Old mac80211 and wireless-drivers
>> trees will not be used anymore.
>> 
>> While at it, add a wiki link to wireless drivers section and a patchwork link
>> to 802.11, mac80211 and rfkill sections.
>> 
>> Acked-by: Johannes Berg <johannes@sipsolutions.net>
>> Signed-off-by: Kalle Valo <kvalo@kernel.org>
>> ---
>> 
>> Stephen, please use these new trees in linux-next from now on.
>
> Done from today.  I have set you and Johannes as contacts along with
> the linux-wireless mailing list.  Also, I assume you meant to mention
> that I should use the branches called "main".

Yes, please use main branches. We decided to try the new naming scheme.
Thanks Stephen.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

      reply	other threads:[~2022-01-15 11:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-14 13:34 [PATCH wireless] MAINTAINERS: add common wireless and wireless-next trees Kalle Valo
2022-01-14 16:19 ` Jakub Kicinski
2022-01-14 17:23   ` Kalle Valo
2022-01-14 21:18 ` Stephen Rothwell
2022-01-15 11:11   ` Kalle Valo [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=87o84ds16t.fsf@kernel.org \
    --to=kvalo@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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).