From: Simon Horman <horms@kernel.org>
To: Shi Hao <i.shihao.999@gmail.com>
Cc: kuba@kernel.org, davem@davemloft.net, dsahern@kernel.org,
edumazet@google.com, herbert@gondor.apana.org.au,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, netdev@vger.kernel.org,
pabeni@redhat.com, pablo@netfilter.org,
steffen.klassert@secunet.com
Subject: Re: [PATCH v2] net: ipv6: fix spelling typos in comments
Date: Sat, 6 Dec 2025 10:15:56 +0000 [thread overview]
Message-ID: <aTQCXJ7MUvnJpG6B@horms.kernel.org> (raw)
In-Reply-To: <20251206083813.240710-1-i.shihao.999@gmail.com>
On Sat, Dec 06, 2025 at 02:08:13PM +0530, Shi Hao wrote:
> Correct misspelled typos in comments
>
> - informations -> information
> - wont -> won't
> - upto -> up to
> - destionation -> destination
>
> Signed-off-by: Shi Hao <i.shihao.999@gmail.com>
Hi Shi Hao,
Unfortunately this patches do not apply cleanly on net-next,
and thus can't be processed by our CI.
When applying manually I see:
Patch failed at 0001 net: ipv6: fix spelling typos in comments
error: corrupt patch at line 58
Also, net-next is currently closed.
## Form letter - net-next-closed
The merge window for v6.19 has begun and therefore net-next has closed
for new drivers, features, code refactoring and optimizations. We are
currently accepting bug fixes only.
Please repost when net-next reopens.
Due to a combination of the merge-window, travel commitments of the
maintainers, and the holiday season, net-next will re-open after
2nd January.
RFC patches sent for review only are welcome at any time.
See: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html#development-cycle
--
pw-bot: changes-requested
next prev parent reply other threads:[~2025-12-06 10:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-06 8:38 [PATCH v2] net: ipv6: fix spelling typos in comments Shi Hao
2025-12-06 10:15 ` Simon Horman [this message]
2025-12-08 5:39 ` ShiHao
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=aTQCXJ7MUvnJpG6B@horms.kernel.org \
--to=horms@kernel.org \
--cc=davem@davemloft.net \
--cc=dsahern@kernel.org \
--cc=edumazet@google.com \
--cc=herbert@gondor.apana.org.au \
--cc=i.shihao.999@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pablo@netfilter.org \
--cc=steffen.klassert@secunet.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;
as well as URLs for NNTP newsgroup(s).