From: Boqun Feng <boqun.feng@gmail.com>
To: Lukas Bulwahn <lbulwahn@redhat.com>
Cc: Viresh Kumar <viresh.kumar@linaro.org>,
kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org,
Lukas Bulwahn <lukas.bulwahn@redhat.com>
Subject: Re: [PATCH] MAINTAINERS: adjust file entry in CPU HOTPLUG
Date: Mon, 16 Jun 2025 08:10:21 -0700 [thread overview]
Message-ID: <aFAz3eKz2gDk9B1N@Mac.home> (raw)
In-Reply-To: <20250616140108.39335-1-lukas.bulwahn@redhat.com>
On Mon, Jun 16, 2025 at 04:01:08PM +0200, Lukas Bulwahn wrote:
> From: Lukas Bulwahn <lukas.bulwahn@redhat.com>
>
> Commit c7f005f70d22 ("rust: cpu: Add CpuId::current() to retrieve current
> CPU ID") adds the file rust/helpers/cpu.c, and intends to add a file entry
> for that file in the MAINTAINERS section CPU HOTPLUG. However, the added
> file entry is rust/helper/cpu.c; note the subtle difference between the two
> file names. Hence, ./scripts/get_maintainer.pl --self-test=patterns
> complains about a broken reference.
>
> Adjust the file entry to the intended file.
>
> Fixes: c7f005f70d22 ("rust: cpu: Add CpuId::current() to retrieve current CPU ID")
> Signed-off-by: Lukas Bulwahn <lukas.bulwahn@redhat.com>
Reviewed-by: Boqun Feng <boqun.feng@gmail.com>
Regards,
Boqun
> ---
> MAINTAINERS | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index ec49e1973425..c23665ac3b3d 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -6263,7 +6263,7 @@ F: include/linux/cpuhotplug.h
> F: include/linux/smpboot.h
> F: kernel/cpu.c
> F: kernel/smpboot.*
> -F: rust/helper/cpu.c
> +F: rust/helpers/cpu.c
> F: rust/kernel/cpu.rs
>
> CPU IDLE TIME MANAGEMENT FRAMEWORK
> --
> 2.49.0
>
next prev parent reply other threads:[~2025-06-16 15:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 14:01 Lukas Bulwahn
2025-06-16 15:10 ` Boqun Feng [this message]
2025-06-19 5:29 ` Viresh Kumar
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=aFAz3eKz2gDk9B1N@Mac.home \
--to=boqun.feng@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=lbulwahn@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas.bulwahn@redhat.com \
--cc=viresh.kumar@linaro.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®