From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Hemanth Selam <hemanth.selam@gmail.com>
Cc: Alexander Aring <alex.aring@gmail.com>,
Stefan Schmidt <stefan@datenfreihafen.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>, Simon Horman <horms@kernel.org>,
linux-wpan@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH wpan-next v2 0/2] ieee802154: fix typos in comments
Date: Mon, 07 Sep 2026 12:07:36 +0200 [thread overview]
Message-ID: <87pkypwf13.fsf@bootlin.com> (raw)
In-Reply-To: <20260907095132.21244-1-hemanth.selam@gmail.com> (Hemanth Selam's message of "Mon, 7 Sep 2026 15:21:30 +0530")
On 07/09/2026 at 15:21:30 +0530, Hemanth Selam <hemanth.selam@gmail.com> wrote:
> Two comment typos under 802.15.4, split per component. Found with scripts/checkpatch.pl using the
> misspelling list in scripts/spelling.txt. Comments only, no code
> changes.
>
> v1 went out with a bare [PATCH] and a "net:" subject prefix. As
> maintainer-netdev.rst asks, v2 designates the patches to a tree, and
> each subject now names the component it touches instead of "net:". The
> series is rebased onto that tree; the diff is unchanged.
I didn't ask for a split, we can abuse the prefix in that case.
You should not have dropped my R-by tag though, given the fact that the
diff is strictly identical.
Reviewed-by: Miquel Raynal <miquel.raynal@bootlin.com>
No need to resend again though.
Thanks,
Miquèl
next prev parent reply other threads:[~2026-09-07 10:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 9:51 Hemanth Selam
2026-09-07 9:51 ` [PATCH wpan-next v2 1/2] ieee802154: at86rf230: fix typo "upto" in comment Hemanth Selam
2026-09-07 9:51 ` [PATCH wpan-next v2 2/2] mac802154: fix typo "substract" " Hemanth Selam
2026-09-07 10:07 ` Miquel Raynal [this message]
2026-09-07 11:42 ` [PATCH wpan-next v2 0/2] ieee802154: fix typos in comments Hemanth Selam
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=87pkypwf13.fsf@bootlin.com \
--to=miquel.raynal@bootlin.com \
--cc=alex.aring@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hemanth.selam@gmail.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wpan@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stefan@datenfreihafen.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®