Hi Stefan, stefan@xxxxxxxxxxxxxxxxxx wrote on Thu, 6 Jan 2022 09:44:50 +0100: > Hello. > > On 06.01.22 01:38, Alexander Aring wrote: > > Hi, > > > > > > On Wed, 5 Jan 2022 at 15:55, Miquel Raynal <miquel.raynal@xxxxxxxxxxx> 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). Sure! It might be worth updating [1] to tell people about this prefix? (only the userspace tools prefix is mentioned). [1] https://linux-wpan.org/contributing.html > 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. Yeah sure, no problem. > 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? Yes of course, that's ideal. Thanks, Miquèl
