From: Simon Horman <horms@kernel.org>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Haakon Bugge <haakon.bugge@oracle.com>,
Allison Henderson <allison.henderson@oracle.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Santosh Shilimkar <ssantosh@kernel.org>,
"stable@vger.kernel.org" <stable@vger.kernel.org>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
OFED mailing list <linux-rdma@vger.kernel.org>,
"rds-devel@oss.oracle.com" <rds-devel@oss.oracle.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net v2] rds: ib: Remove unused extern definition
Date: Thu, 4 Sep 2025 19:45:48 +0100 [thread overview]
Message-ID: <20250904184548.GK372207@horms.kernel.org> (raw)
In-Reply-To: <20250904073343.1138ce24@kernel.org>
On Thu, Sep 04, 2025 at 07:33:43AM -0700, Jakub Kicinski wrote:
> On Thu, 4 Sep 2025 14:22:02 +0000 Haakon Bugge wrote:
> > Sorry if I have mis-interpreted the collateral. From [1], I quote:
> >
> > "A Fixes: tag indicates that the patch fixes an issue in a previous
> > commit." As such, it is an "issue" and I reference the offending
> > commit.
>
> You're not the first one to misinterpret it, I guess we should fix the
> doc :$
+1
FTR, a fix implies a bug. And a good rule of thumb that a bug
is something broken that is user-visible. E.g. a system panic.
>
> > As to "Cc: stable", you're quite right. My bad. You want a v3 or are
> > you (and stable) able to handle it?
>
> Please repost this one without the extra tags, and if you want it to go
> via netdev the subject tag should be net-next in this case (it will end
> up in 6.18)
prev parent reply other threads:[~2025-09-04 18:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 11:53 [PATCH net v2] rds: ib: Remove unused extern definition Håkon Bugge
2025-09-04 13:55 ` Jakub Kicinski
2025-09-04 14:22 ` Haakon Bugge
2025-09-04 14:33 ` Jakub Kicinski
2025-09-04 18:45 ` Simon Horman [this message]
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=20250904184548.GK372207@horms.kernel.org \
--to=horms@kernel.org \
--cc=allison.henderson@oracle.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=haakon.bugge@oracle.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rds-devel@oss.oracle.com \
--cc=ssantosh@kernel.org \
--cc=stable@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).