From: Lukas Bulwahn <lukas.bulwahn@gmail.com> To: Dwaipayan Ray <dwaipayanray1@gmail.com> Cc: Joe Perches <joe@perches.com>, linux-kernel-mentees@lists.linuxfoundation.org, Linux Kernel Mailing List <linux-kernel@vger.kernel.org> Subject: Re: [PATCH] checkpatch: fix typo and remove duplicate word Date: Fri, 13 Nov 2020 14:34:36 +0100 [thread overview] Message-ID: <CAKXUXMwsvj6Y3dEq-eAOyCoJV3qhV7K9U_uRrtbg9u4TV0zyeA@mail.gmail.com> (raw) In-Reply-To: <20201113131037.37519-1-dwaipayanray1@gmail.com> On Fri, Nov 13, 2020 at 2:11 PM Dwaipayan Ray <dwaipayanray1@gmail.com> wrote: > > Delete repeated word in scripts/checkpatch.pl. > "are are" -> "are" > > Fix typo "commments" -> "comments" > > Signed-off-by: Dwaipayan Ray <dwaipayanray1@gmail.com> Does this make checkpatch.pl pass checkpatch without any further warnings? Nice idea to check if checkpatch.pl still fulfills the checkpatch rules we created... Lukas > --- > scripts/checkpatch.pl | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl > index 2749f32dffe9..e7fd2d6279cf 100755 > --- a/scripts/checkpatch.pl > +++ b/scripts/checkpatch.pl > @@ -2841,7 +2841,7 @@ sub process { > > > # stable@vger.kernel.org or stable@kernel.org shouldn't > - # have an email name. In addition commments should strictly > + # have an email name. In addition comments should strictly > # begin with a # > if ($email =~ /^.*stable\@(?:vger\.)?kernel\.org/i) { > if (($comment ne "" && $comment !~ /^#.+/) || > @@ -7109,7 +7109,7 @@ sub process { > exit(0); > } > > - # This is not a patch, and we are are in 'no-patch' mode so > + # This is not a patch, and we are in 'no-patch' mode so > # just keep quiet. > if (!$chk_patch && !$is_patch) { > exit(0); > -- > 2.27.0 >
WARNING: multiple messages have this Message-ID (diff)
From: Lukas Bulwahn <lukas.bulwahn@gmail.com> To: Dwaipayan Ray <dwaipayanray1@gmail.com> Cc: Joe Perches <joe@perches.com>, linux-kernel-mentees@lists.linuxfoundation.org, Linux Kernel Mailing List <linux-kernel@vger.kernel.org> Subject: Re: [Linux-kernel-mentees] [PATCH] checkpatch: fix typo and remove duplicate word Date: Fri, 13 Nov 2020 14:34:36 +0100 [thread overview] Message-ID: <CAKXUXMwsvj6Y3dEq-eAOyCoJV3qhV7K9U_uRrtbg9u4TV0zyeA@mail.gmail.com> (raw) In-Reply-To: <20201113131037.37519-1-dwaipayanray1@gmail.com> On Fri, Nov 13, 2020 at 2:11 PM Dwaipayan Ray <dwaipayanray1@gmail.com> wrote: > > Delete repeated word in scripts/checkpatch.pl. > "are are" -> "are" > > Fix typo "commments" -> "comments" > > Signed-off-by: Dwaipayan Ray <dwaipayanray1@gmail.com> Does this make checkpatch.pl pass checkpatch without any further warnings? Nice idea to check if checkpatch.pl still fulfills the checkpatch rules we created... Lukas > --- > scripts/checkpatch.pl | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) > > diff --git a/scripts/checkpatch.pl b/scripts/checkpatch.pl > index 2749f32dffe9..e7fd2d6279cf 100755 > --- a/scripts/checkpatch.pl > +++ b/scripts/checkpatch.pl > @@ -2841,7 +2841,7 @@ sub process { > > > # stable@vger.kernel.org or stable@kernel.org shouldn't > - # have an email name. In addition commments should strictly > + # have an email name. In addition comments should strictly > # begin with a # > if ($email =~ /^.*stable\@(?:vger\.)?kernel\.org/i) { > if (($comment ne "" && $comment !~ /^#.+/) || > @@ -7109,7 +7109,7 @@ sub process { > exit(0); > } > > - # This is not a patch, and we are are in 'no-patch' mode so > + # This is not a patch, and we are in 'no-patch' mode so > # just keep quiet. > if (!$chk_patch && !$is_patch) { > exit(0); > -- > 2.27.0 > _______________________________________________ Linux-kernel-mentees mailing list Linux-kernel-mentees@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
next prev parent reply other threads:[~2020-11-13 13:34 UTC|newest] Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-13 13:10 [PATCH] checkpatch: fix typo and remove duplicate word Dwaipayan Ray 2020-11-13 13:10 ` [Linux-kernel-mentees] " Dwaipayan Ray 2020-11-13 13:34 ` Lukas Bulwahn [this message] 2020-11-13 13:34 ` Lukas Bulwahn 2020-11-13 13:48 ` Dwaipayan Ray 2020-11-13 13:48 ` [Linux-kernel-mentees] " Dwaipayan Ray 2020-11-13 13:57 Dwaipayan Ray 2020-11-13 15:00 ` Joe Perches 2020-11-13 15:08 ` Dwaipayan Ray
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=CAKXUXMwsvj6Y3dEq-eAOyCoJV3qhV7K9U_uRrtbg9u4TV0zyeA@mail.gmail.com \ --to=lukas.bulwahn@gmail.com \ --cc=dwaipayanray1@gmail.com \ --cc=joe@perches.com \ --cc=linux-kernel-mentees@lists.linuxfoundation.org \ --cc=linux-kernel@vger.kernel.org \ /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: linkBe 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.