From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Joe Perches <joe@perches.com>
Cc: linux-kernel@vger.kernel.org, Andy Whitcroft <apw@canonical.com>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Akhilesh Patil <akhilesh@ee.iitb.ac.in>
Subject: Re: [PATCH v3 1/1] checkpatch: Don't warn on "orhapned" DT schema file
Date: Tue, 28 Oct 2025 09:54:31 +0200 [thread overview]
Message-ID: <aQB2t3gD8cQ0fJv0@smile.fi.intel.com> (raw)
In-Reply-To: <4484f1dfe22c9ca6dcad52d915a92f600d0088e1.camel@perches.com>
On Mon, Oct 27, 2025 at 08:45:08AM -0700, Joe Perches wrote:
> On Mon, 2025-10-27 at 10:36 +0100, Andy Shevchenko wrote:
> > Currently checkpatch warns is the DT schema file is absent in MAINTAINERS.
> > However the DT schema files are self-contained in this sense and
> > have embedded information about maintainers of it. This is a requirement.
> > Hence, avoid checkpatch warning about it.
> >
> > Tested-by: Akhilesh Patil <akhilesh@ee.iitb.ac.in>
> > Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
>
> nackish.
>
> Perhaps it'd be better to make checkpatch and get_maintainer have
> some list of filename suffixes that are expected to have embedded
> maintainer email addresses
>
> Maybe something like:
>
> our $maintainer_in_file_types = '\.(?:yaml|dts.?|rst)$';
Please, do that. I have no idea where all these Perl files do the necessary bits.
But currently we have a problem (false positives) with checkpatch, and some
maintainers dislike them.
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2025-10-28 7:54 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 9:36 Andy Shevchenko
2025-10-27 15:45 ` Joe Perches
2025-10-28 7:54 ` Andy Shevchenko [this message]
2025-10-28 8:05 ` Markus Elfring
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=aQB2t3gD8cQ0fJv0@smile.fi.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=akhilesh@ee.iitb.ac.in \
--cc=apw@canonical.com \
--cc=dwaipayanray1@gmail.com \
--cc=joe@perches.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@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 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®