From: Krzysztof Kozlowski <krzk@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: linux-kernel@vger.kernel.org, Andy Whitcroft <apw@canonical.com>,
Joe Perches <joe@perches.com>,
Dwaipayan Ray <dwaipayanray1@gmail.com>,
Lukas Bulwahn <lukas.bulwahn@gmail.com>,
Akhilesh Patil <akhilesh@ee.iitb.ac.in>
Subject: Re: [PATCH v2 1/1] checkpatch: Don't warn on "orhapned" DT schema file
Date: Mon, 27 Oct 2025 10:41:12 +0100 [thread overview]
Message-ID: <c5b86849-b09d-4e81-b357-53f511e087ae@kernel.org> (raw)
In-Reply-To: <aP885cVvKxE5xMBW@smile.fi.intel.com>
On 27/10/2025 10:35, Andy Shevchenko wrote:
> On Mon, Oct 27, 2025 at 10:25:58AM +0100, Krzysztof Kozlowski wrote:
>> On 27/10/2025 10:17, 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.
>>>
>>> Requested-by: Krzysztof Kozlowski <krzk@kernel.org>
>>
>> No, that's not true.
>>
>> First, there is no such tag.
>
> No, that's not true.
>
> $ git log --oneline --grep ^Requested-by: | wc -l
No, you do like this:
git grep Requested-by
and then find it in the list of approved tags.
> 357
>
>> Second, I never requested it.
>>
>> NAK
>
> Fair enough, I'll drop the tag.
It's not even solving the problem you wanted. You claimed there is some
sort of problem that maintainer update is one at last patch of patchset.
I claimed that there is no, because it is standard and completely fine
way of doing things and whatever checkpatch is reported is just false
positive.
You did not fix that false positive.
Best regards,
Krzysztof
prev parent reply other threads:[~2025-10-27 9:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-27 9:17 [PATCH v2 1/1] checkpatch: Don't warn on "orhapned" DT schema file Andy Shevchenko
2025-10-27 9:25 ` Krzysztof Kozlowski
2025-10-27 9:35 ` Andy Shevchenko
2025-10-27 9:41 ` Krzysztof Kozlowski [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=c5b86849-b09d-4e81-b357-53f511e087ae@kernel.org \
--to=krzk@kernel.org \
--cc=akhilesh@ee.iitb.ac.in \
--cc=andriy.shevchenko@linux.intel.com \
--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