[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87r151gpsr.fsf@posteo.de>
Date: Tue, 10 May 2022 19:17:56 +0000
From: Manuel Ullmann <labre@...teo.de>
To: Paolo Abeni <pabeni@...hat.com>
Cc: Manuel Ullmann <labre@...teo.de>,
Igor Russkikh <irusskikh@...vell.com>,
linux-kernel@...r.kernel.org, netdev@...r.kernel.org,
regressions@...ts.linux.dev, davem@...emloft.net,
ndanilov@...vell.com, kuba@...nel.org, edumazet@...gle.com,
Jordan Leppert <jordanleppert@...tonmail.com>,
Holger Hoffstaette <holger@...lied-asynchrony.com>,
koo5 <kolman.jindrich@...il.com>
Subject: Re: [PATCH v6] net: atlantic: always deep reset on pm op, fixing up
my null deref regression
Paolo Abeni <pabeni@...hat.com> writes:
> On Sun, 2022-05-08 at 00:36 +0000, Manuel Ullmann wrote:
>> [...]
>
> For future submission, please always specify the target tree (which is
> -net in this case). No need to resubmit: I'm applying it.
>
> Thanks,
>
> Paolo
Ah, okay. So next branches are reserved for new changes, while non-next
may be targeted by fixups or at least regression fixes. I can't recall a
definition for this in the documentation, but that might be me. I'll
keep this in mind for the future. Thanks for applying it and bearing
with me.
Regards,
Manuel
Powered by blists - more mailing lists