[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87cz5btf2i.fsf@meer.lwn.net>
Date: Tue, 14 Mar 2023 11:31:33 -0600
From: Jonathan Corbet <corbet@....net>
To: Xujun Leng <lengxujun2007@....com>
Cc: linux@...mhuis.info, lengxujun2007@....com,
linux-doc@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] docs: process: submitting-patches: fix typo in section
"Respond to review comments"
Xujun Leng <lengxujun2007@....com> writes:
> In the second paragraph of section "Respond to review comments", there is
> a spelling mistake: "aganst" should be "against".
>
> Signed-off-by: Xujun Leng <lengxujun2007@....com>
> ---
> Documentation/process/submitting-patches.rst | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/Documentation/process/submitting-patches.rst b/Documentation/process/submitting-patches.rst
> index eac7167dce83..69ce64e03c70 100644
> --- a/Documentation/process/submitting-patches.rst
> +++ b/Documentation/process/submitting-patches.rst
> @@ -320,7 +320,7 @@ for their time. Code review is a tiring and time-consuming process, and
> reviewers sometimes get grumpy. Even in that case, though, respond
> politely and address the problems they have pointed out. When sending a next
> version, add a ``patch changelog`` to the cover letter or to individual patches
> -explaining difference aganst previous submission (see
> +explaining difference against previous submission (see
> :ref:`the_canonical_patch_format`).
Applied, thanks.
jon
Powered by blists - more mailing lists