From: Krzysztof Kozlowski <krzk@kernel.org>
To: Jihed Chaibi <jihed.chaibi.dev@gmail.com>,
heiko@sntech.de, briannorris@chromium.org
Cc: devicetree@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-kernel-mentees@lists.linux.dev, skhan@linuxfoundation.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] Fixing a minor typo in YAML document
Date: Sat, 17 May 2025 13:21:27 +0200 [thread overview]
Message-ID: <62bd6757-c4d0-42c1-a76d-abea18a8a55e@kernel.org> (raw)
In-Reply-To: <20250517020552.737932-1-jihed.chaibi.dev@gmail.com>
On 17/05/2025 04:05, Jihed Chaibi wrote:
> A small typo in the rockchip,rk3399 YAML document ;
> "less then" should become: "less than"
>
> Signed-off-by: Jihed Chaibi <jihed.chaibi.dev@gmail.com>
> ---
> .../bindings/memory-controllers/rockchip,rk3399-dmc.yaml | 6 +++---
You not only skipped me as DT maintainer for this file but also skipped
me as the actual subsystem maintainer.
<form letter>
Please use scripts/get_maintainers.pl to get a list of necessary people
and lists to CC (and consider --no-git-fallback argument, so you will
not CC people just because they made one commit years ago). It might
happen, that command when run on an older kernel, gives you outdated
entries. Therefore please be sure you base your patches on recent Linux
kernel.
Tools like b4 or scripts/get_maintainer.pl provide you proper list of
people, so fix your workflow. Tools might also fail if you work on some
ancient tree (don't, instead use mainline) or work on fork of kernel
(don't, instead use mainline). Just use b4 and everything should be
fine, although remember about `b4 prep --auto-to-cc` if you added new
patches to the patchset.
</form letter>
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-05-17 11:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-17 2:05 [PATCH 1/1] Fixing a minor typo in YAML document Jihed Chaibi
2025-05-17 11:21 ` Krzysztof Kozlowski [this message]
2025-05-17 12:05 ` Jihed Chaibi
2025-05-18 10:34 ` Krzysztof Kozlowski
2025-05-18 12:06 ` Jihed Chaibi
2025-05-22 8:13 ` Brigham Campbell
2025-05-19 20:03 ` Brian Norris
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=62bd6757-c4d0-42c1-a76d-abea18a8a55e@kernel.org \
--to=krzk@kernel.org \
--cc=briannorris@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=jihed.chaibi.dev@gmail.com \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=skhan@linuxfoundation.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