From: Daniel Jordan <daniel.m.jordan@oracle.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, Vladimir Oltean <olteanv@gmail.com>,
netdev@vger.kernel.org,
Steffen Klassert <steffen.klassert@secunet.com>,
linux-crypto@vger.kernel.org, Jonathan Corbet <corbet@lwn.net>,
linux-doc@vger.kernel.org, Mukesh Ojha <quic_mojha@quicinc.com>
Subject: Re: [PATCH 03/24] Documentation: core-api: correct spelling
Date: Thu, 9 Feb 2023 10:20:04 -0500 [thread overview]
Message-ID: <20230209152004.n2tk5wr4exnah7xt@parnassus.localdomain> (raw)
In-Reply-To: <20230209071400.31476-4-rdunlap@infradead.org>
On Wed, Feb 08, 2023 at 11:13:39PM -0800, Randy Dunlap wrote:
> 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>
Acked-by: Daniel Jordan <daniel.m.jordan@oracle.com>
> ---
> Documentation/core-api/packing.rst | 2 +-
> Documentation/core-api/padata.rst | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff -- a/Documentation/core-api/packing.rst b/Documentation/core-api/packing.rst
> --- a/Documentation/core-api/packing.rst
> +++ b/Documentation/core-api/packing.rst
> @@ -161,6 +161,6 @@ xxx_packing() that calls it using the pr
>
> The packing() function returns an int-encoded error code, which protects the
> programmer against incorrect API use. The errors are not expected to occur
> -durring runtime, therefore it is reasonable for xxx_packing() to return void
> +during runtime, therefore it is reasonable for xxx_packing() to return void
> and simply swallow those errors. Optionally it can dump stack or print the
> error description.
> diff -- a/Documentation/core-api/padata.rst b/Documentation/core-api/padata.rst
> --- a/Documentation/core-api/padata.rst
> +++ b/Documentation/core-api/padata.rst
> @@ -42,7 +42,7 @@ padata_shells associated with it, each a
> Modifying cpumasks
> ------------------
>
> -The CPUs used to run jobs can be changed in two ways, programatically with
> +The CPUs used to run jobs can be changed in two ways, programmatically with
> padata_set_cpumask() or via sysfs. The former is defined::
>
> int padata_set_cpumask(struct padata_instance *pinst, int cpumask_type,
next prev parent reply other threads:[~2023-02-09 15:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-09 7:13 [PATCH 00/24 v2] Documentation: correct lots of spelling errors (series 1) Randy Dunlap
2023-02-09 7:13 ` [PATCH 03/24] Documentation: core-api: correct spelling Randy Dunlap
2023-02-09 15:20 ` Daniel Jordan [this message]
2023-02-11 0:26 ` Jakub Kicinski
2023-02-09 7:13 ` [PATCH 08/24] Documentation: isdn: " Randy Dunlap
2023-02-11 0:30 ` [PATCH 00/24 v2] Documentation: correct lots of spelling errors (series 1) patchwork-bot+netdevbpf
2023-06-26 6:56 ` Krzysztof Wilczyński
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=20230209152004.n2tk5wr4exnah7xt@parnassus.localdomain \
--to=daniel.m.jordan@oracle.com \
--cc=corbet@lwn.net \
--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=quic_mojha@quicinc.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).