From: Greg KH <gregkh@linuxfoundation.org>
To: Richard Weinberger <richard@nod.at>
Cc: linux-kernel@vger.kernel.org, bhe@redhat.com,
sourabhjain@linux.ibm.com, akpm@linux-foundation.org,
senozhatsky@chromium.org, john.ogness@linutronix.de,
rostedt@goodmis.org, pmladek@suse.com,
upstream+linux@sigma-star.at
Subject: Re: [PATCH] ksysfs: Expose hardware name
Date: Mon, 23 Feb 2026 14:49:31 +0100 [thread overview]
Message-ID: <2026022306-macaw-cringing-19c2@gregkh> (raw)
In-Reply-To: <20260223133448.411343-1-richard@nod.at>
On Mon, Feb 23, 2026 at 02:34:48PM +0100, Richard Weinberger wrote:
> Userspace tools often require a short, descriptive name of the hardware
> platform. Currently, this information is fragmented: Device Tree-based
> platforms typically use /proc/device-tree/model, while x86 platforms
> combine multiple values from /sys/class/dmi/id/. There is no uniform,
> platform-agnostic way to retrieve this string.
>
> The kernel already maintains dump_stack_arch_desc_str[], which contains
> the model name or DMI values used for the "Hardware name:" field in
> stack traces.
>
> Expose dump_stack_arch_desc_str[] at /sys/kernel/hardware_name to
> provide userspace with a consistent interface for identifying the
> underlying hardware.
No objection from me, but now that this is a global symbol in the
kernel, "dump_" seems like an odd prefix for this. How about
"linux_hardware_name" to match up with the sysfs file name?
</bikeshed>
thanks,
greg k-h
next prev parent reply other threads:[~2026-02-23 13:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 13:34 [PATCH] ksysfs: Expose hardware name Richard Weinberger
2026-02-23 13:49 ` Greg KH [this message]
2026-02-23 13:53 ` Richard Weinberger
2026-02-23 13:55 ` John Ogness
2026-02-23 14:20 ` Richard Weinberger
2026-02-25 9:00 ` Steven Rostedt
2026-03-12 14:17 ` Petr Mladek
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=2026022306-macaw-cringing-19c2@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=richard@nod.at \
--cc=rostedt@goodmis.org \
--cc=senozhatsky@chromium.org \
--cc=sourabhjain@linux.ibm.com \
--cc=upstream+linux@sigma-star.at \
/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