All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hemanth Selam <hemanth.selam@gmail.com>
To: Miquel Raynal <miquel.raynal@bootlin.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,  7 Sep 2026 17:12:02 +0530	[thread overview]
Message-ID: <20260907114203.40171-1-hemanth.selam@gmail.com> (raw)
In-Reply-To: <87pkypwf13.fsf@bootlin.com>

On Mon, 07 Sep 2026, Miquel Raynal wrote:
> You should not have dropped my R-by tag though, given the fact that the
> diff is strictly identical.

You are right, and I am sorry.  The diff was unchanged, so your tag should
have been carried over.  I rebuilt the series from the commits rather than
from the posted patches and lost the trailer on the way; that is my
mistake, not something you should have had to chase.

Thanks for re-giving it, and for the note on the split.  I split by
component because maintainer-netdev.rst asks the prefix to name the code
being touched, and I could not see how to name both drivers/net/ieee802154
and net/mac802154 in one prefix.  Abusing the prefix is fine by me next
time.

I will not resend, as you asked.

      reply	other threads:[~2026-09-07 11:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-07  9:51 [PATCH wpan-next v2 0/2] ieee802154: fix typos in comments 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 ` [PATCH wpan-next v2 0/2] ieee802154: fix typos in comments Miquel Raynal
2026-09-07 11:42   ` Hemanth Selam [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=20260907114203.40171-1-hemanth.selam@gmail.com \
    --to=hemanth.selam@gmail.com \
    --cc=alex.aring@gmail.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wpan@vger.kernel.org \
    --cc=miquel.raynal@bootlin.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.