All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Bagas Sanjaya <bagasdotme@gmail.com>,
	Shaomin Deng <dengshaomin@cdjrlc.com>,
	viro@zeniv.linux.org.uk, brauner@kernel.org
Cc: linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
	Mao Zhu <zhumao001@208suo.com>
Subject: Re: [PATCH] fs: Fix comment typo
Date: Sun, 11 Jun 2023 13:50:34 -0600	[thread overview]
Message-ID: <87edmhok1h.fsf@meer.lwn.net> (raw)
In-Reply-To: <ZIXEHHvkJVlmE_c4@debian.me>

Bagas Sanjaya <bagasdotme@gmail.com> writes:

> On Sun, Jun 11, 2023 at 08:33:14AM -0400, Shaomin Deng wrote:
>> From: Mao Zhu <zhumao001@208suo.com>
>> 
>> Delete duplicated word in comment.
>
> On what function?

Bagas, do I *really* have to ask you, yet again, to stop nitpicking our
contributors into the ground?  It appears I do.  So:

Bagas, *stop* this.  It's a typo patch removing an extraneous word.  The
changelog is fine.  We absolutely do not need you playing changelog cop
and harassing contributors over this kind of thing.

>> Signed-off-by: Mao Zhu <zhumao001@208suo.com>
>
> You're carrying someone else's patch, so besides SoB from original
> author, you need to also have your own SoB.

This, instead, is a valid problem that needs to be fixed.

Thanks,

jon

  reply	other threads:[~2023-06-11 19:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-11 12:33 [PATCH] fs: Fix comment typo Shaomin Deng
2023-06-11 12:54 ` Bagas Sanjaya
2023-06-11 19:50   ` Jonathan Corbet [this message]
2023-06-11 20:07     ` Matthew Wilcox
2023-06-12  2:00       ` Bagas Sanjaya
2023-06-12  1:41     ` Bagas Sanjaya
2023-06-12  1:53       ` Bagas Sanjaya
2023-06-12  6:34     ` Christian Brauner
2023-06-12  8:34       ` Christian Brauner
2023-06-12  9:18         ` Bagas Sanjaya
2023-06-12  6:31 ` Christian Brauner
  -- strict thread matches above, loose matches on Subject: below --
2022-08-21 15:25 [PATCH] fs: fix " Roger Knecht
2022-08-22 16:38 ` Simon Glass

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=87edmhok1h.fsf@meer.lwn.net \
    --to=corbet@lwn.net \
    --cc=bagasdotme@gmail.com \
    --cc=brauner@kernel.org \
    --cc=dengshaomin@cdjrlc.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=viro@zeniv.linux.org.uk \
    --cc=zhumao001@208suo.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.