mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Xujun Leng <lengxujun2007@126.com>
Cc: linux@leemhuis.info, lengxujun2007@126.com,
	linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] docs: process: submitting-patches: fix typo in section "Respond to review comments"
Date: Tue, 14 Mar 2023 11:31:33 -0600	[thread overview]
Message-ID: <87cz5btf2i.fsf@meer.lwn.net> (raw)
In-Reply-To: <20230312071423.3042-1-lengxujun2007@126.com>

Xujun Leng <lengxujun2007@126.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@126.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

      reply	other threads:[~2023-03-14 17:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-12  7:14 Xujun Leng
2023-03-14 17:31 ` Jonathan Corbet [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=87cz5btf2i.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=lengxujun2007@126.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@leemhuis.info \
    /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

all inboxes | Powered by JetHome®