From: Manuel Ullmann <labre@posteo.de>
To: Paolo Abeni <pabeni@redhat.com>
Cc: Manuel Ullmann <labre@posteo.de>,
Igor Russkikh <irusskikh@marvell.com>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
regressions@lists.linux.dev, davem@davemloft.net,
ndanilov@marvell.com, kuba@kernel.org, edumazet@google.com,
Jordan Leppert <jordanleppert@protonmail.com>,
Holger Hoffstaette <holger@applied-asynchrony.com>,
koo5 <kolman.jindrich@gmail.com>
Subject: Re: [PATCH v6] net: atlantic: always deep reset on pm op, fixing up my null deref regression
Date: Tue, 10 May 2022 19:17:56 +0000 [thread overview]
Message-ID: <87r151gpsr.fsf@posteo.de> (raw)
In-Reply-To: <b140c37fe1aac315e07464dd6a2d7a8f463e6fe4.camel@redhat.com> (Paolo Abeni's message of "Tue, 10 May 2022 10:37:24 +0200")
Paolo Abeni <pabeni@redhat.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
next prev parent reply other threads:[~2022-05-10 19:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-08 0:36 [PATCH v6] net: atlantic: always deep reset on pm op, fixing up my null deref regression Manuel Ullmann
2022-05-10 8:37 ` Paolo Abeni
2022-05-10 19:17 ` Manuel Ullmann [this message]
2022-05-10 8:40 ` patchwork-bot+netdevbpf
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=87r151gpsr.fsf@posteo.de \
--to=labre@posteo.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=holger@applied-asynchrony.com \
--cc=irusskikh@marvell.com \
--cc=jordanleppert@protonmail.com \
--cc=kolman.jindrich@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ndanilov@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=regressions@lists.linux.dev \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.