From: Carlos Llamas <cmllamas@google.com>
To: Joe Perches <joe@perches.com>
Cc: stable@vger.kernel.org, Andy Whitcroft <apw@canonical.com>,
kernel-team@android.com, Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Aditya Srivastava <yashsri421@gmail.com>,
Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>
Subject: Re: [PATCH 5.10 1/2] checkpatch: add new exception to repeated word check
Date: Thu, 14 Dec 2023 18:52:21 +0000 [thread overview]
Message-ID: <ZXtO5Ym8vFDRdn1j@google.com> (raw)
In-Reply-To: <8f7d59b8945a2205ea7acf66da23d4673e48f166.camel@perches.com>
On Thu, Dec 14, 2023 at 10:31:02AM -0800, Joe Perches wrote:
> On Thu, 2023-12-14 at 18:15 +0000, Carlos Llamas wrote:
> > From: Dwaipayan Ray <dwaipayanray1@gmail.com>
> >
> > commit 1db81a682a2f2a664489c4e94f3b945f70a43a13 upstream.
> >
> > Recently, commit 4f6ad8aa1eac ("checkpatch: move repeated word test")
> > moved the repeated word test to check for more file types. But after
> > this, if checkpatch.pl is run on MAINTAINERS, it generates several
> > new warnings of the type:
> >
> > WARNING: Possible repeated word: 'git'
>
> Why should this be backported? Who cares?
>
Our CI for stable cares. However, it seems it would be best to run the
version directly from master instead. I'll try that. Sorry for the
noise.
next prev parent reply other threads:[~2023-12-14 18:52 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-14 18:15 [PATCH 5.10 0/2] checkpatch: fix repeated word annoyance Carlos Llamas
2023-12-14 18:15 ` [PATCH 5.10 1/2] checkpatch: add new exception to repeated word check Carlos Llamas
2023-12-14 18:31 ` Joe Perches
2023-12-14 18:52 ` Carlos Llamas [this message]
2023-12-14 18:15 ` [PATCH 5.10 2/2] checkpatch: fix false positives in REPEATED_WORD warning Carlos Llamas
2023-12-14 18:23 ` [PATCH 5.10 0/2] checkpatch: fix repeated word annoyance Greg KH
2023-12-14 18:37 ` Carlos Llamas
2023-12-15 7:15 ` Greg KH
2023-12-15 16:46 ` Carlos Llamas
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=ZXtO5Ym8vFDRdn1j@google.com \
--to=cmllamas@google.com \
--cc=akpm@linux-foundation.org \
--cc=apw@canonical.com \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=kernel-team@android.com \
--cc=lukas.bulwahn@gmail.com \
--cc=stable@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=yashsri421@gmail.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.