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>
Subject: Re: [PATCH v2 1/1] drivers/base/cpu: Print kernel arch
Date: Fri, 29 Jul 2022 15:55:32 +0200 [thread overview]
Message-ID: <YuPm1HioKV7W1G7u@pevik> (raw)
In-Reply-To: <YuPlUOT1nFyT9Fm7@kroah.com>
Hi Greg,
> On Fri, Jul 29, 2022 at 02:53:44PM +0200, Petr Vorel wrote:
> > Hi all,
> > > 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>
> > > ---
> > Changes v1->v2:
> > * Add file into /proc/sys/kernel/ (previously it was in
> > /sys/devices/system/cpu/). There are
> Looks like this line ended too soon?
OK, Friday. I'm sorry to be too abstracted today.
I was about to explain the reason - that there are other related files
osrelease, ostype.
> > * Update Documentation/ABI/ (Greg)
> This looks good to me, I'll queue it up after the next -rc1 is out
> unless someone objects.
Thanks!
Kind regards,
Petr
> greg k-h
next prev parent reply other threads:[~2022-07-29 13:55 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 [this message]
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
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=YuPm1HioKV7W1G7u@pevik \
--to=pvorel@suse.cz \
--cc=dsterba@suse.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