[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <57f0e761-db5a-86f6-ab27-c0943d3e7805@datenfreihafen.org>
Date: Thu, 6 Jan 2022 09:44:50 +0100
From: Stefan Schmidt <stefan@...enfreihafen.org>
To: Alexander Aring <alex.aring@...il.com>,
Miquel Raynal <miquel.raynal@...tlin.com>
Cc: Nicolas Schodet <nico@...fr.eu.org>,
"David S. Miller" <davem@...emloft.net>,
Jakub Kicinski <kuba@...nel.org>,
"open list:NETWORKING [GENERAL]" <netdev@...r.kernel.org>,
linux-wpan - ML <linux-wpan@...r.kernel.org>,
David Girault <david.girault@...vo.com>,
Romuald Despres <romuald.despres@...vo.com>,
Frederic Blain <frederic.blain@...vo.com>,
Thomas Petazzoni <thomas.petazzoni@...tlin.com>,
kernel list <linux-kernel@...r.kernel.org>
Subject: Re: [net-next 12/18] net: mac802154: Handle scan requests
Hello.
On 06.01.22 01:38, Alexander Aring wrote:
> Hi,
>
>
> On Wed, 5 Jan 2022 at 15:55, Miquel Raynal <miquel.raynal@...tlin.com> wrote:
> ...
>> Also, just for the record,
>> - should I keep copying the netdev list for v2?
>
> yes, why not.
>> - should I monitor if net-next is open before sending or do you have
>> your own set of rules?
>>
>
> I need to admit, Stefan is the "Thanks, applied." hero here and he
> should answer this question.
No need to monitor if net-next is open for these patches (just don't add
a net-next patch subject prefix as this would confuse Jakub and Dave.
wpan-next would be more appropriate).
I am following this patchset and the review from Alex. I have not done a
full in depth review myself yet, its on my list.
Basically keep working with Alex and use the wpan-next prefix and I will
pick up the patches to my wpan-next tree and sent a pull to net-next
when we are happy with it. Does that sound good to you?
regards
Stefan Schmidt
Powered by blists - more mailing lists