lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87o84ds16t.fsf@kernel.org>
Date:   Sat, 15 Jan 2022 13:11:54 +0200
From:   Kalle Valo <kvalo@...nel.org>
To:     Stephen Rothwell <sfr@...b.auug.org.au>
Cc:     linux-wireless@...r.kernel.org, netdev@...r.kernel.org,
        linux-kernel@...r.kernel.org, lkp@...el.com
Subject: Re: [PATCH wireless] MAINTAINERS: add common wireless and wireless-next trees

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

> Hi Kalle,
>
> On Fri, 14 Jan 2022 15:34:15 +0200 Kalle Valo <kvalo@...nel.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@...solutions.net>
>> Signed-off-by: Kalle Valo <kvalo@...nel.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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ