From: Simon Horman <horms@kernel.org>
To: Alexander Zubkov <green@qrator.net>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org, linux@treblig.org
Subject: Re: [PATCH net-next] Fix misspelling of "accept*" in net
Date: Wed, 9 Oct 2024 13:44:55 +0100 [thread overview]
Message-ID: <20241009124455.GT99782@kernel.org> (raw)
In-Reply-To: <20241008162756.22618-2-green@qrator.net>
On Tue, Oct 08, 2024 at 06:27:57PM +0200, Alexander Zubkov wrote:
> Several files have "accept*" misspelled as "accpet*" in the comments.
> Fix all such occurrences.
>
> Signed-off-by: Alexander Zubkov <green@qrator.net>
Thanks, I agree this corrects the spelling of accept in these files.
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2024-10-09 12:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 16:27 [PATCH net-next] Fix misspelling of "accept*" in net Alexander Zubkov
2024-10-09 12:44 ` Simon Horman [this message]
2024-10-10 3:10 ` 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=20241009124455.GT99782@kernel.org \
--to=horms@kernel.org \
--cc=green@qrator.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@treblig.org \
--cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).