mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: netdev-bot+sashiko@kernel.org
To: dhowells@redhat.com
Cc: netdev@vger.kernel.org, marc.dionne@auristor.com,
	kuba@kernel.org, davem@davemloft.net, edumazet@google.com,
	pabeni@redhat.com, horms@kernel.org,
	linux-afs@lists.infradead.org, linux-kernel@vger.kernel.org,
	jaltman@auristor.com, stable@vger.kernel.org
Subject: Re: [PATCH net 1/2] rxrpc: Fix the comments saying RFC8958 to be RFC8985
Date: Tue, 29 Sep 2026 19:29:46 +0000	[thread overview]
Message-ID: <179071018682.434549.14159424380322602012@kernel.org> (raw)
In-Reply-To: <20260925191520.2206700-2-dhowells@redhat.com>

Thank you for your contribution! Sashiko AI review found more severe
issue(s) in other patches of this series. This mail is only an FYI, in case
you want to address the nit picks below when you respin.

Low priority / nit picks for your consideration:

- [Low] Commit "rxrpc: Fix the comments saying RFC8958 to be RFC8985"
  only changes comments.

--

rxrpc: Fix the comments saying RFC8958 to be RFC8985

This commit fixes comments in net/rxrpc/input_rack.c and
net/rxrpc/ar-internal.h that cited RFC8958 when they meant RFC8985, the
RACK-TLP loss detection algorithm for TCP. Only comments change. The
compiled output is the same.

> Fixes: 7c482665931b ("rxrpc: Implement RACK/TLP to deal with transmission stalls [RFC8985]")
> Signed-off-by: David Howells <dhowells@redhat.com>

[ ... ]

> cc: linux-afs@lists.infradead.org
> cc: stable@vger.kernel.org

[Severity: Low]
This isn't a bug, but should the stable Cc be here?

Each hunk swaps RFC8958 for RFC8985 in a comment, for example the file
header in input_rack.c:

-/* RACK-TLP [RFC8958] Implementation
+/* RACK-TLP [RFC8985] Implementation

Documentation/process/stable-kernel-rules.rst says:

  - No "trivial" fixes without benefit for users (spelling changes, whitespace
    cleanups, etc).

The Cc also doesn't seem needed as a prerequisite for the next patch in
the series, "rxrpc: Fix RACK-TLP implementation". That patch's hunks and
context lines don't touch any of the comments edited here. It changes
rxrpc_rack_mark_lost(), the bodies of rxrpc_rack_update_reo_wnd(),
rxrpc_rack_detect_loss() and rxrpc_tlp_calc_pto(), and the struct fields
under the "RACK-TLP [RFC8985] state" comment, which was already correct.
The functional fix should therefore apply cleanly without this patch.

Could the stable Cc be dropped, and would this patch fit better in
net-next than in net?

-- 
Sashiko AI review · https://netdev-ai.bots.linux.dev/sashiko/#/patchset/20260925191520.2206700-1-dhowells%40redhat.com

  reply	other threads:[~2026-09-29 19:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-25 19:15 [PATCH net 0/2] rxrpc: RACK-TLP fixes David Howells
2026-09-25 19:15 ` [PATCH net 1/2] rxrpc: Fix the comments saying RFC8958 to be RFC8985 David Howells
2026-09-29 19:29   ` netdev-bot+sashiko [this message]
2026-09-25 19:15 ` [PATCH net 2/2] rxrpc: Fix RACK-TLP implementation David Howells
2026-09-29 19:29   ` netdev-bot+sashiko

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=179071018682.434549.14159424380322602012@kernel.org \
    --to=netdev-bot+sashiko@kernel.org \
    --cc=davem@davemloft.net \
    --cc=dhowells@redhat.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=jaltman@auristor.com \
    --cc=kuba@kernel.org \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=marc.dionne@auristor.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --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

all inboxes | Powered by JetHome®