From: Joe Perches <joe@perches.com>
To: Masahiro Yamada <yamada.masahiro@socionext.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: checkpatch: false positive "does MAINTAINERS need updating?" warning
Date: Sun, 06 Oct 2019 23:52:02 -0700 [thread overview]
Message-ID: <b5b363ef96a1bfad6965c4b01c8737990b8f4e91.camel@perches.com> (raw)
In-Reply-To: <CAK7LNARKUAoHDFzGJ3snAy2XeQshTqmzDMUC7qqU8=L-p=+LNg@mail.gmail.com>
On Mon, 2019-10-07 at 13:44 +0900, Masahiro Yamada wrote:
> Hi Joe,
>
>
> I ran checkpatch.pl against the following:
> https://lore.kernel.org/patchwork/patch/1136334/
>
>
> I did update MAINTAINERS, but I still get
> "does MAINTAINERS need updating?" warning.
> Why?
Because checkpatch is not able to determine
that you updated MAINTAINERS correctly.
Ignore checkpatch output when you know better.
>
>
> $ scripts/checkpatch.pl
> 0001-doc-move-namespaces.rst-out-of-kbuild-directory.patch
> WARNING: added, moved or deleted file(s), does MAINTAINERS need updating?
> #18:
> Documentation/{kbuild => admin-guide}/namespaces.rst | 0
>
> total: 0 errors, 1 warnings, 14 lines checked
>
> NOTE: For some of the reported defects, checkpatch may be able to
> mechanically convert to the typical style using --fix or --fix-inplace.
>
> 0001-doc-move-namespaces.rst-out-of-kbuild-directory.patch has style
> problems, please review.
>
> NOTE: If any of the errors are false positives, please report
> them to the maintainer, see CHECKPATCH in MAINTAINERS.
>
>
prev parent reply other threads:[~2019-10-07 6:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-07 4:44 Masahiro Yamada
2019-10-07 6:52 ` Joe Perches [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=b5b363ef96a1bfad6965c4b01c8737990b8f4e91.camel@perches.com \
--to=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=yamada.masahiro@socionext.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 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®