public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: Simon Horman <horms@kernel.org>
Cc: Ethan Nelson-Moore <enelsonmoore@gmail.com>,
	 netdev@vger.kernel.org, linux-usb@vger.kernel.org,
	 Andrew Lunn <andrew+netdev@lunn.ch>,
	 "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: usb: sr9700: fix byte numbering in comments
Date: Thu, 15 Jan 2026 21:22:44 +0100	[thread overview]
Message-ID: <87jyxiy6az.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <aWklu0EwMbINC6T0@horms.kernel.org> (Simon Horman's message of "Thu, 15 Jan 2026 17:36:59 +0000")

>>>>> "Simon" == Simon Horman <horms@kernel.org> writes:

 > On Mon, Jan 12, 2026 at 11:53:21PM -0800, Ethan Nelson-Moore wrote:
 >> The comments describing the RX/TX headers and status response use
 >> a combination of 0- and 1-based indexing, leading to confusion. Correct
 >> the numbering and make it consistent. Also fix a typo "pm" for "pn".
 >> 
 >> This issue also existed in dm9601 and was fixed in commit 61189c78bda8
 >> ("dm9601: trivial comment fixes").
 >> 
 >> Signed-off-by: Ethan Nelson-Moore <enelsonmoore@gmail.com>

 > Thanks,

 > I agree this is consistent with the cited commit.

 > Reviewed-by: Simon Horman <horms@kernel.org>

 > Context left below for the benefit of Peter who I've added to the CC list.

Heh, old stuff ;)

Acked-by: Peter Korsgaard <peter@korsgaard.com>

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2026-01-15 20:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-13  7:53 [PATCH net-next] net: usb: sr9700: fix byte numbering in comments Ethan Nelson-Moore
2026-01-15 17:36 ` Simon Horman
2026-01-15 20:22   ` Peter Korsgaard [this message]
2026-01-16  3:50 ` 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=87jyxiy6az.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=enelsonmoore@gmail.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-usb@vger.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