linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Joe Perches <joe@perches.com>
To: "Andersen, John" <john.s.andersen@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] checkpatch.pl Is "does MAINTAINERS need updating" check broken?
Date: Wed, 18 Nov 2020 20:00:32 -0800	[thread overview]
Message-ID: <95a1e8f15358bbc6e11f88880cc7927f6b0f83ea.camel@perches.com> (raw)
In-Reply-To: <20201119040123.GA629660@johnsa1-desk.jf.intel.com>

On Wed, 2020-11-18 at 20:01 -0800, Andersen, John wrote:
> I just noticed that patches which have "added, moved or deleted file(s)" and
> updated MAINTAINERS still trigger the following warning:

Please to not directly message me.
Send any questions to the lkml list and cc me.



       reply	other threads:[~2020-11-19  4:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201119040123.GA629660@johnsa1-desk.jf.intel.com>
2020-11-19  4:00 ` Joe Perches [this message]
2020-11-19 15:52 [RFC] checkpatch.pl Is "does MAINTAINERS need updating" check broken? Andersen, John

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=95a1e8f15358bbc6e11f88880cc7927f6b0f83ea.camel@perches.com \
    --to=joe@perches.com \
    --cc=john.s.andersen@intel.com \
    --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: 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;
as well as URLs for NNTP newsgroup(s).