Message ID | 20230611123314.5282-1-dengshaomin@cdjrlc.com |
---|---|
State | New |
Headers |
Return-Path: <linux-kernel-owner@vger.kernel.org> Delivered-To: ouuuleilei@gmail.com Received: by 2002:a59:994d:0:b0:3d9:f83d:47d9 with SMTP id k13csp2013978vqr; Sun, 11 Jun 2023 05:38:16 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ6Y4mzqSd3eGItpZMlyp4PD1utthlZlW8PE8UXRhoMYLGF0jSZfB0VztqIvwLCKAfA+PGrV X-Received: by 2002:a05:6a20:e48d:b0:118:62d9:b0a6 with SMTP id ni13-20020a056a20e48d00b0011862d9b0a6mr4904603pzb.4.1686487095664; Sun, 11 Jun 2023 05:38:15 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1686487095; cv=none; d=google.com; s=arc-20160816; b=OlVNJEmIEs91eg7zDPFXV1zJPwhfSK5io1/XNv83wy5bD440fFW5jPARAm36XzQ7S6 JxcnjQobl2wg4s/CoLXckDQWp1bAbO+Hivg2wx+ZrBsQEc34279JjPAnlxXiFKSlvZNf TK5n6U3Z8cZ+4355GrVBpruDMtwvqr2CUKNYSJ424UzjBb/j8RDVR8ZPXa6pw54pMtiw GI3Z9L/EkvF2bouksPHFBIgXnD0bz7Fzg8a4JRizArUuW02xbBa40s5rnMv4s2kScs6D Kz8WtFJYLSBzBd+LgmLrlCQ/hV6N5VSjoc8ks+Qe4FI/s1klCuksZWRyIHvkZSHy3gN2 WcDw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:feedback-id:content-transfer-encoding :mime-version:message-id:date:subject:cc:to:from; bh=eB+QgkX0qf8VPIZI3QhtFKszMytxFmFIpm1weme69qQ=; b=xupLkPab0stiHnveTcUmNfr5XD/Hacv665qcZFjqwoEK6IvuBPE10lnf5xlOqEOIxN ojq97HLN80mFZv322qvVXzsfwvE0NazA+et6QzAzZj4ILAwTBJXzFJ3fBKfnQ+jRtM9O 0PbqRC7Pku9I/Td3w8Saqhm6s8B/u7sujAkhaLn4BhavOrtiIkULVqbBJgRsCESVmEcB FKfo8t3xB9zoygAXMRv/1G4nEpw4hN1+Ur9Y2CnKJ1Nc7uPdLka3sA81nPH3WZWTCc1+ /0Qc/SKtodoXOK2l8Rj+KCu3GUxpIFRcXYl7ZUsXF2LsOd9kvwHpVpSbhnpI8FTBACmn TPew== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id k191-20020a636fc8000000b0053b8c964128si5738363pgc.708.2023.06.11.05.37.58; Sun, 11 Jun 2023 05:38:15 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232772AbjFKMfX (ORCPT <rfc822;liningstudo@gmail.com> + 99 others); Sun, 11 Jun 2023 08:35:23 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:48390 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229562AbjFKMfU (ORCPT <rfc822;linux-kernel@vger.kernel.org>); Sun, 11 Jun 2023 08:35:20 -0400 X-Greylist: delayed 99 seconds by postgrey-1.37 at lindbergh.monkeyblade.net; Sun, 11 Jun 2023 05:35:17 PDT Received: from bg4.exmail.qq.com (bg4.exmail.qq.com [43.154.54.12]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E9678113; Sun, 11 Jun 2023 05:35:17 -0700 (PDT) X-QQ-mid: bizesmtp64t1686486807t0zq682e Received: from localhost.localdomain ( [182.148.15.16]) by bizesmtp.qq.com (ESMTP) with id ; Sun, 11 Jun 2023 20:33:15 +0800 (CST) X-QQ-SSF: 01000000000000D0I000000A0000000 X-QQ-FEAT: f+ZzKTjTzV3oDnnoAz7NwYgbWoGgDpMUsA4vwvuyeDaZEC7EFCdIIo0bVlTpZ jAebU6jNUqzPKA5TjUWMLxImtGBsZXhMpLAwK9SQ9kMEGDUPaMdPFlCYO6wxLMYKuy4TKZy xt9nV5guq7X7cCz+7hGDE90i/4cBOFn+A/lAed5I9mVrR64yH9n+C5unmeoSM9AI8iJlmS/ gDf0lyojIoXFItjTZPspGo9fd34u4ukSJ0ZI1lDH2iLDk0rNk1AgovfhJdtw9PSn8HQjufw AgnJo0wD+RVg3/HG1wmCRSnXF4pJEQoG4O2dvOX+crzkxbHPMIeeVBxZu45Sk+oPKHNLbeu 2nXphW/3kB+PYCcsWo= X-QQ-GoodBg: 0 X-BIZMAIL-ID: 296039327464568289 From: Shaomin Deng <dengshaomin@cdjrlc.com> To: 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: [PATCH] fs: Fix comment typo Date: Sun, 11 Jun 2023 08:33:14 -0400 Message-Id: <20230611123314.5282-1-dengshaomin@cdjrlc.com> X-Mailer: git-send-email 2.35.1 MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-QQ-SENDSIZE: 520 Feedback-ID: bizesmtp:cdjrlc.com:qybglogicsvrgz:qybglogicsvrgz5a-0 X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL,SPF_HELO_NONE,SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: <linux-kernel.vger.kernel.org> X-Mailing-List: linux-kernel@vger.kernel.org X-getmail-retrieved-from-mailbox: =?utf-8?q?INBOX?= X-GMAIL-THRID: =?utf-8?q?1768409892826838363?= X-GMAIL-MSGID: =?utf-8?q?1768409892826838363?= |
Series |
fs: Fix comment typo
|
|
Commit Message
Shaomin Deng
June 11, 2023, 12:33 p.m. UTC
From: Mao Zhu <zhumao001@208suo.com> Delete duplicated word in comment. Signed-off-by: Mao Zhu <zhumao001@208suo.com> --- include/linux/fs.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
Comments
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? > > 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. > --- > include/linux/fs.h | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/include/linux/fs.h b/include/linux/fs.h > index df6c1817906f..aa870b77cc2b 100644 > --- a/include/linux/fs.h > +++ b/include/linux/fs.h > @@ -2675,7 +2675,7 @@ extern void evict_inodes(struct super_block *sb); > void dump_mapping(const struct address_space *); > > /* > - * Userspace may rely on the the inode number being non-zero. For example, glibc > + * Userspace may rely on the inode number being non-zero. For example, glibc > * simply ignores files with zero i_ino in unlink() and other places. > * > * As an additional complication, if userspace was compiled with I don't see the function name in above diff (dump_mapping() isn't the function I mean). Regardless, the fix LGTM. @cdjrlc.com developers: I'm really, really fed up with you ignoring review comments. It seems like you have issues on your mail setup. Fix your mailer! Until then, I just say NAK. Thanks.
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
On Sun, Jun 11, 2023 at 01:50:34PM -0600, Jonathan Corbet wrote: > 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. Amen. > >> 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. I mean ... yes, technically, it does. But it's a change that deletes a word in a comment. Honestly, I'd take the patch without any kind of sign-off. It doesn't create any copyright claim, which is the purpose of the DCO.
On Sun, Jun 11, 2023 at 01:50:34PM -0600, Jonathan Corbet wrote: > 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. OK, thanks for reminding me again. At the time of reviewing, I had bad feeling that @cdjrlc.com people will ignore review comments (I betted due to mail setup problem that prevents them from properly repling to mailing lists, which is unfortunate). I was nitpicking because the diff context doesn't look clear to me (what function name?). > > >> 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. OK. Sorry for my inconvenience.
On 6/12/23 08:41, Bagas Sanjaya wrote: > On Sun, Jun 11, 2023 at 01:50:34PM -0600, Jonathan Corbet wrote: >> 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. > > OK, thanks for reminding me again. > > At the time of reviewing, I had bad feeling that @cdjrlc.com people will > ignore review comments (I betted due to mail setup problem that prevents > them from properly repling to mailing lists, which is unfortunate). I > was nitpicking because the diff context doesn't look clear to me (what > function name?). > And no wonder why several maintainers also highlight this (which prompted me to review that way): [1]: https://lore.kernel.org/all/162b5545-7d24-3cf2-9158-3100ef644e03@linux.intel.com/ [2]: https://lore.kernel.org/all/3a73cf7f02915891c77dc5a3203dc187f6d91194.camel@HansenPartnership.com/
On Sun, Jun 11, 2023 at 09:07:22PM +0100, Matthew Wilcox wrote: > On Sun, Jun 11, 2023 at 01:50:34PM -0600, Jonathan Corbet wrote: > > 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. > > Amen. > Amen too. Hope I can learn from this. > > >> 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. > > I mean ... yes, technically, it does. But it's a change that deletes > a word in a comment. Honestly, I'd take the patch without any kind of > sign-off. It doesn't create any copyright claim, which is the purpose > of the DCO. What? Relaxed SoB requirement for trivial patches like this? I thought that SoB rules also apply to these patches. Thanks.
On Sun, 11 Jun 2023 08:33:14 -0400, Shaomin Deng wrote: > Delete duplicated word in comment. > > Missing sender SOB added. --- Applied to the vfs.misc branch of the vfs/vfs.git tree. Patches in the vfs.misc branch should appear in linux-next soon. Please report any outstanding bugs that were missed during review in a new review to the original patch series allowing us to drop it. It's encouraged to provide Acked-bys and Reviewed-bys even though the patch has now been applied. If possible patch trailers will be updated. tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git branch: vfs.misc [1/1] fs: Fix comment typo https://git.kernel.org/vfs/vfs/c/dce5a4da3cf5
On Sun, Jun 11, 2023 at 01:50:34PM -0600, Jonathan Corbet wrote: > 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. 100% agreed. > > >> 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. Patch picked up and missing sender SOB added.
On Mon, Jun 12, 2023 at 08:34:53AM +0200, Christian Brauner wrote: > On Sun, Jun 11, 2023 at 01:50:34PM -0600, Jonathan Corbet wrote: > > 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. > > 100% agreed. > > > > > >> 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. > > Patch picked up and missing sender SOB added. I've been informed that I may not be allowed to do that. So dropping the sender SOB for now following willy's argument.
On 6/12/23 15:34, Christian Brauner wrote: >> Patch picked up and missing sender SOB added. > > I've been informed that I may not be allowed to do that. > So dropping the sender SOB for now following willy's argument. OK, thanks for resolving!
diff --git a/include/linux/fs.h b/include/linux/fs.h index df6c1817906f..aa870b77cc2b 100644 --- a/include/linux/fs.h +++ b/include/linux/fs.h @@ -2675,7 +2675,7 @@ extern void evict_inodes(struct super_block *sb); void dump_mapping(const struct address_space *); /* - * Userspace may rely on the the inode number being non-zero. For example, glibc + * Userspace may rely on the inode number being non-zero. For example, glibc * simply ignores files with zero i_ino in unlink() and other places. * * As an additional complication, if userspace was compiled with