From: Simon Horman <horms@kernel.org>
To: Leon Kral <leon.j.kral@protonmail.com>
Cc: john.fastabend@gmail.com, kuba@kernel.org, sd@queasysnail.net,
chuck.lever@oracle.com, davem@davemloft.net, edumazet@google.com,
pabeni@redhat.com, corbet@lwn.net, skhan@linuxfoundation.org,
netdev@vger.kernel.org, kernel-tls-handshake@lists.linux.dev,
linux-kernel@vger.kernel.org, linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation/networking/tls-handshake.rst: Fix of minor grammar mistake
Date: Thu, 26 Feb 2026 17:44:58 +0000 [thread overview]
Message-ID: <aaCGmqqMMPey4nbL@horms.kernel.org> (raw)
In-Reply-To: <20260226000915.27898-1-leon.j.kral@protonmail.com>
On Thu, Feb 26, 2026 at 12:04:54AM +0000, Leon Kral wrote:
> The word "a" was used instead of "an" which is grammatically incorrect.
> Fix by changing from "a" to "an". This improves readability of the
> documentation.
>
> Signed-off-by: Leon Kral <leon.j.kral@protonmail.com>
Hi Leon,
Your change looks good to me.
But looking over git history it seems that an appropriate
prefix for the patch would be 'net/handshake:'.
And it would be best to set the target tree explicitly,
in this case net-next seems appropriate. So:
Subject: [PATCH net-next v2] net/handshake: ...
It also might be best to make the subject rest of the subject,
while not making it too long. But I'll leave that up to you.
Please do make sure that 24h elapses since you posted v1 before posting v2.
For more information on the Netdev development process please
see: https://www.kernel.org/doc/html/next/process/maintainer-netdev.html
...
--
pw-bot: changes-requested
prev parent reply other threads:[~2026-02-26 17:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 0:04 [PATCH] Documentation/networking/tls-handshake.rst: Fix of minor grammar mistake Leon Kral
2026-02-26 17:44 ` Simon Horman [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=aaCGmqqMMPey4nbL@horms.kernel.org \
--to=horms@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=corbet@lwn.net \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=john.fastabend@gmail.com \
--cc=kernel-tls-handshake@lists.linux.dev \
--cc=kuba@kernel.org \
--cc=leon.j.kral@protonmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sd@queasysnail.net \
--cc=skhan@linuxfoundation.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