From: Johannes Berg <johannes@sipsolutions.net>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Alexander Lobakin <aleksander.lobakin@intel.com>,
netdev@vger.kernel.org, Jesper Dangaard Brouer <hawk@kernel.org>,
Ilias Apalodimas <ilias.apalodimas@linaro.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net-next] net: page_pool: fix warning code
Date: Fri, 05 Jul 2024 16:23:43 +0200 [thread overview]
Message-ID: <09edde00d5d44505b7a41efdfb26cb16d0cbdc59.camel@sipsolutions.net> (raw)
In-Reply-To: <7eab05e6-4192-4888-9b6a-6427dc709623@lunn.ch>
On Fri, 2024-07-05 at 16:19 +0200, Andrew Lunn wrote:
> On Fri, Jul 05, 2024 at 02:33:31PM +0200, Johannes Berg wrote:
> > On Fri, 2024-07-05 at 14:32 +0200, Alexander Lobakin wrote:
> > > From: Johannes Berg <johannes@sipsolutions.net>
> > > Date: Fri, 5 Jul 2024 13:42:06 +0200
> > >
> > > > From: Johannes Berg <johannes.berg@intel.com>
> > > >
> > > > WARN_ON_ONCE("string") doesn't really do what appears to
> > > > be intended, so fix that.
> > > >
> > > > Signed-off-by: Johannes Berg <johannes.berg@intel.com>
> > >
> > > "Fixes:" tag?
> >
> > There keep being discussions around this so I have no idea what's the
> > guideline-du-jour ... It changes the code but it's not really an issue?
>
> https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html
And ... by referring to that you just made a guideline(-du-jour!) that
"Fixes" tag must be accompanied by "Cc: stable@" (because Fixes
_doesn't_ imply stable backport!), and then you apply the stable rules
to that.
The time that any one of us will (have) spent even reading this thread
is clearly longer than it would've taken to add (if desired) or remove
(had I included it and not desired) the tag in the first place ...
johannes
next prev parent reply other threads:[~2024-07-05 14:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 11:42 [PATCH net-next] net: page_pool: fix warning code Johannes Berg
2024-07-05 12:32 ` Alexander Lobakin
2024-07-05 12:33 ` Johannes Berg
2024-07-05 12:37 ` Alexander Lobakin
2024-07-05 12:39 ` Johannes Berg
2024-07-05 13:14 ` Przemek Kitszel
2024-07-05 13:28 ` Alexander Lobakin
2024-07-05 13:38 ` Przemek Kitszel
2024-07-05 14:19 ` Andrew Lunn
2024-07-05 14:23 ` Johannes Berg [this message]
2024-07-05 14:33 ` Alexander Lobakin
2024-07-05 14:36 ` Johannes Berg
2024-07-05 14:44 ` Alexander Lobakin
2024-07-09 3: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=09edde00d5d44505b7a41efdfb26cb16d0cbdc59.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=aleksander.lobakin@intel.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hawk@kernel.org \
--cc=ilias.apalodimas@linaro.org \
--cc=kuba@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox