From: Mukesh Ojha <quic_mojha@quicinc.com>
To: <rdunlap@infradead.org>
Cc: <corbet@lwn.net>, <daniel.m.jordan@oracle.com>,
<linux-crypto@vger.kernel.org>, <linux-doc@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <netdev@vger.kernel.org>,
<olteanv@gmail.com>, <steffen.klassert@secunet.com>
Subject: Re: [PATCH 05/35] Documentation: core-api: correct spelling
Date: Fri, 27 Jan 2023 20:55:07 +0530 [thread overview]
Message-ID: <1674833107-10526-1-git-send-email-quic_mojha@quicinc.com> (raw)
In-Reply-To: <20230127064005.1558-6-rdunlap@infradead.org>
>Correct spelling problems for Documentation/core-api/ as reported
>by codespell.
>Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
>Cc: Vladimir Oltean <olteanv@gmail.com>
>Cc: netdev@vger.kernel.org
>Cc: Steffen Klassert <steffen.klassert@secunet.com>
>Cc: Daniel Jordan <daniel.m.jordan@oracle.com>
>Cc: linux-crypto@vger.kernel.org
>Cc: Jonathan Corbet <corbet@lwn.net>
>Cc: linux-doc@vger.kernel.org
Reviewed-by: Mukesh Ojha <quic_mojha@quicinc.com>
-Mukesh
next prev parent reply other threads:[~2023-01-27 15:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 6:39 [PATCH 00/35] Documentation: correct lots of spelling errors (series 1) Randy Dunlap
2023-01-27 6:39 ` [PATCH 05/35] Documentation: core-api: correct spelling Randy Dunlap
2023-01-27 15:25 ` Mukesh Ojha [this message]
2023-01-27 6:39 ` [PATCH 13/35] Documentation: isdn: " Randy Dunlap
2023-01-28 6:06 ` Jakub Kicinski
2023-01-28 10:48 ` (subset) [PATCH 00/35] Documentation: correct lots of spelling errors (series 1) Mark Brown
2023-01-28 20:30 ` patchwork-bot+netdevbpf
2023-01-31 16:28 ` (subset) " Catalin Marinas
2023-02-14 16:57 ` Martin K. Petersen
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=1674833107-10526-1-git-send-email-quic_mojha@quicinc.com \
--to=quic_mojha@quicinc.com \
--cc=corbet@lwn.net \
--cc=daniel.m.jordan@oracle.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=rdunlap@infradead.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).