From: Hemanth Selam <hemanth.selam@gmail.com>
To: Xuanqiang Luo <xuanqiang.luo@linux.dev>
Cc: osmocom-net-gprs@lists.osmocom.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org,
Pablo Neira Ayuso <pablo@netfilter.org>,
Harald Welte <laforge@gnumonks.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: fix repeated word 'to' in comment
Date: Mon, 7 Sep 2026 15:01:38 +0530 [thread overview]
Message-ID: <20260907093138.24589-1-hemanth.selam@gmail.com> (raw)
In-Reply-To: <aa963ff1-0cfb-48de-ba76-d37467676a78@linux.dev>
On Mon, Sep 07, 2026 at 04:16:00PM +0800, Xuanqiang Luo wrote:
> Typo fixes are cleanups.
> Please specify the target tree: use [PATCH net-next] instead of a bare
> [PATCH].
You are right, and thank you for the correction. I missed
maintainer-netdev.rst on this; it asks for the tree in the subject and I
sent these with a bare [PATCH].
The same document also asks not to repost within 24 hours, so rather
than resend immediately I will send v2 tomorrow as
[PATCH net-next] gtp: fix repeated word 'to' in comment
which also fixes the subject prefix, since "net:" does not name the file
being touched. I will do the same for the other patches I sent to
netdev today, and use the right tree for the wireless and wpan ones.
Hemanth
next prev parent reply other threads:[~2026-09-07 9:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 6:38 Hemanth Selam
2026-09-07 8:16 ` Xuanqiang Luo
2026-09-07 9:31 ` Hemanth Selam [this message]
2026-09-09 21:00 ` 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=20260907093138.24589-1-hemanth.selam@gmail.com \
--to=hemanth.selam@gmail.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=laforge@gnumonks.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=osmocom-net-gprs@lists.osmocom.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=xuanqiang.luo@linux.dev \
/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®