From: Steven Rostedt <rostedt@goodmis.org>
To: Richard Weinberger <richard@nod.at>
Cc: John Ogness <john.ogness@linutronix.de>,
linux-kernel <linux-kernel@vger.kernel.org>, bhe <bhe@redhat.com>,
sourabhjain <sourabhjain@linux.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
senozhatsky <senozhatsky@chromium.org>,
Petr Mladek <pmladek@suse.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
upstream+linux <upstream+linux@sigma-star.at>
Subject: Re: [PATCH] ksysfs: Expose hardware name
Date: Wed, 25 Feb 2026 04:00:59 -0500 [thread overview]
Message-ID: <20260225040059.5a857a80@fedora> (raw)
In-Reply-To: <40046959.4372.1771856422459.JavaMail.zimbra@nod.at>
On Mon, 23 Feb 2026 15:20:22 +0100 (CET)
Richard Weinberger <richard@nod.at> wrote:
> ----- Ursprüngliche Mail -----
> > Von: "John Ogness" <john.ogness@linutronix.de>
> > An: "richard" <richard@nod.at>, "linux-kernel" <linux-kernel@vger.kernel.org>
> >
> > It seems a bit odd to make this a dependency of CONFIG_PRINTK. Perhaps
> > @dump_stack_arch_desc_str and dump_stack_set_arch_desc() should move out
> > of lib/dump_stack.c if this new sysfs attribute is accepted?
>
> Sure. I was surprised too that lib/dump_stack.c depends on CONFIG_PRINTK.
>
Or possibly we should make dump_stack.c not depend on CONFIG_PRINTK.
I'm guessing that it was done that way because it expects to dump the
stack to the console?
(haven't looked at the code yet)
-- Steve
next prev parent reply other threads:[~2026-02-25 9:01 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
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 [this message]
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=20260225040059.5a857a80@fedora \
--to=rostedt@goodmis.org \
--cc=akpm@linux-foundation.org \
--cc=bhe@redhat.com \
--cc=gregkh@linuxfoundation.org \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pmladek@suse.com \
--cc=richard@nod.at \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.