From: Petr Vorel <pvorel@suse.cz>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org,
"Rafael J. Wysocki" <rafael@kernel.org>,
David Sterba <dsterba@suse.com>,
Eric Biederman <ebiederm@xmision.com>
Subject: Re: [PATCH v2 1/1] drivers/base/cpu: Print kernel arch
Date: Thu, 1 Sep 2022 17:47:03 +0200 [thread overview]
Message-ID: <YxDT9xxMSFLu3xDI@pevik> (raw)
In-Reply-To: <YxDBvD5XrbLApWMy@kroah.com>
Hi Greg,
[ Cc Eric Biederman as the author of kernel/utsname_sysctl.c ]
> On Fri, Jul 29, 2022 at 02:51:41PM +0200, Petr Vorel wrote:
> > Print the machine hardware name (UTS_MACHINE) in /proc/sys/kernel/arch.
> > This helps people who debug kernel with initramfs with minimal
> > environment (i.e. without coreutils or even busybox) or allow to open
> > sysfs file instead of run 'uname -m' in high level languages.
> > Signed-off-by: Petr Vorel <pvorel@suse.cz>
> > ---
> > Documentation/admin-guide/sysctl/kernel.rst | 5 +++++
> > kernel/utsname_sysctl.c | 7 +++++++
> > 2 files changed, 12 insertions(+)
> Wait, why does the subject line say "drivers/base/cpu"? That's not a
> file being touched in this commit at all, so this isn't for me to take
> :(
Thanks for info. My bad, I forget to update the subject.
I can send v3 with corrected subject, but who is going to take this?
$ ./scripts/get_maintainer.pl kernel/utsname_sysctl.c
linux-kernel@vger.kernel.org (open list)
There is listed Author: Eric Biederman, so is it him to Cc ?
Kind regards,
Petr
> thanks,
> greg k-h
next prev parent reply other threads:[~2022-09-01 15:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-29 12:51 [PATCH v2 1/1] drivers/base/cpu: Print kernel arch Petr Vorel
2022-07-29 12:53 ` Petr Vorel
2022-07-29 13:49 ` Greg Kroah-Hartman
2022-07-29 13:55 ` Petr Vorel
2022-08-17 9:56 ` Petr Vorel
2022-08-17 11:16 ` Greg Kroah-Hartman
2022-08-17 19:37 ` Petr Vorel
2022-09-01 14:29 ` Greg Kroah-Hartman
2022-09-01 15:47 ` Petr Vorel [this message]
2022-09-01 16:02 ` Greg Kroah-Hartman
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=YxDT9xxMSFLu3xDI@pevik \
--to=pvorel@suse.cz \
--cc=dsterba@suse.com \
--cc=ebiederm@xmision.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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