From: Jinjie Ruan <ruanjinjie@huawei.com>
To: Krzysztof Kozlowski <krzk@kernel.org>, <lee@kernel.org>,
<linux-kernel@vger.kernel.org>, <jic23@kernel.org>
Subject: Re: [PATCH -next 00/12] mfd: Use for_each_child_of_node_scoped()
Date: Mon, 26 Aug 2024 16:58:13 +0800 [thread overview]
Message-ID: <794f15e7-e15c-a70d-1e72-b5bc570eeab9@huawei.com> (raw)
In-Reply-To: <33abcd58-8a08-4ca7-812f-3de07cca9c92@kernel.org>
On 2024/8/26 16:29, Krzysztof Kozlowski wrote:
> On 26/08/2024 10:28, Jinjie Ruan wrote:
>> Use scoped for_each_available_child_of_node_scoped() when iterating over
>> device nodes to make code a bit simpler.
>>
>> Jinjie Ruan (12):
>> mfd: max77620: Use for_each_child_of_node_scoped()
>> mfd: qcom-spmi-pmic: Use for_each_child_of_node_scoped()
>> mtd: rawnand: arasan: Use for_each_child_of_node_scoped()
>
>
> No, you are mixing different subsystems. And even did not care to Cc
> their maintainers.
OK, I'll resend them.
>
> <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). 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>
Sorry, the low scrip which wrap the `scripts/get_maintainer.pl` has a bug.
>
> Best regards,
> Krzysztof
>
prev parent reply other threads:[~2024-08-26 8:58 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 8:28 Jinjie Ruan
2024-08-26 8:28 ` [PATCH -next 01/12] mfd: max77620: " Jinjie Ruan
2024-08-26 8:28 ` [PATCH -next 02/12] mfd: qcom-spmi-pmic: " Jinjie Ruan
2024-08-26 8:28 ` [PATCH -next 03/12] mtd: rawnand: arasan: " Jinjie Ruan
2024-08-26 8:28 ` [PATCH -next 04/12] mtd: rawnand: cadence: " Jinjie Ruan
2024-08-26 8:28 ` [PATCH -next 05/12] mtd: rawnand: pl353: " Jinjie Ruan
2024-08-26 8:28 ` [PATCH -next 06/12] mtd: rawnand: marvell: drm/rockchip: " Jinjie Ruan
2024-08-26 8:28 ` [PATCH -next 07/12] mtd: rawnand: rockchip: " Jinjie Ruan
2024-08-26 8:28 ` [PATCH -next 08/12] mtd: rawnand: meson: " Jinjie Ruan
2024-08-26 8:28 ` [PATCH -next 09/12] mtd: rawnand: mtk: " Jinjie Ruan
2024-08-26 8:28 ` [PATCH -next 10/12] mtd: rawnand: renesas: " Jinjie Ruan
2024-08-26 8:28 ` [PATCH -next 11/12] mtd: rawnand: stm32_fmc2: " Jinjie Ruan
2024-08-26 8:28 ` [PATCH -next 12/12] mtd: rawnand: sunxi: " Jinjie Ruan
2024-08-26 8:29 ` [PATCH -next 00/12] mfd: " Krzysztof Kozlowski
2024-08-26 8:58 ` Jinjie Ruan [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=794f15e7-e15c-a70d-1e72-b5bc570eeab9@huawei.com \
--to=ruanjinjie@huawei.com \
--cc=jic23@kernel.org \
--cc=krzk@kernel.org \
--cc=lee@kernel.org \
--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
all inboxes | Powered by JetHome®