From: Arnd Bergmann <arnd@arndb.de>
To: linux-aspeed@lists.ozlabs.org
Subject: [PATCH v3 1/3] firmware: Add boot information to sysfs
Date: Fri, 22 Apr 2022 11:05:46 +0200 [thread overview]
Message-ID: <CAK8P3a0G_xNQ6b2e71VXPVi+-j5L--SU37gFErwGYuh1QPrr1A@mail.gmail.com> (raw)
In-Reply-To: <YmJPRPhfA4Cki85S@kroah.com>
On Fri, Apr 22, 2022 at 8:46 AM Greg Kroah-Hartman
<gregkh@linuxfoundation.org> wrote:
> On Fri, Feb 04, 2022 at 05:52:32PM +1030, Joel Stanley wrote:
> > +What: /sys/firmware/bootinfo/*
> > +Date: Jan 2022
>
> It isn't January anymore :)
The patch was sent on Feb 4, I would expect that to be close enough. Does this
need to be the month of the kernel release it is merged into instead?
> > +Description:
> > + A system can expose information about how it was started in
> > + this directory.
>
> I do not understand what you mean by "how it was started".
>
> > + This information is agnostic as to the firmware implementation.
>
> How? This should be very firmware specific.
The original patch was specific to a particular SoC vendor. Since the
information provided here is fairly generic in the end, I asked for
the interface
to be generalized to the point that it can be reused across multiple
vendors and architectures.
Arnd
next prev parent reply other threads:[~2022-04-22 9:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-04 7:22 [PATCH v3 0/3] firmware: Add boot information to sysfs Joel Stanley
2022-02-04 7:22 ` [PATCH v3 1/3] " Joel Stanley
2022-04-22 6:46 ` Greg Kroah-Hartman
2022-04-22 9:05 ` Arnd Bergmann [this message]
2022-04-22 12:26 ` Greg Kroah-Hartman
2022-02-04 7:22 ` [PATCH v3 2/3] ARM: aspeed: Add secure boot controller support Joel Stanley
2022-02-04 7:22 ` [PATCH v3 3/3] x86/setup: Populate bootinfo with secure boot status Joel Stanley
2022-04-22 6:48 ` [PATCH v3 0/3] firmware: Add boot information to sysfs 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=CAK8P3a0G_xNQ6b2e71VXPVi+-j5L--SU37gFErwGYuh1QPrr1A@mail.gmail.com \
--to=arnd@arndb.de \
--cc=linux-aspeed@lists.ozlabs.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;
as well as URLs for NNTP newsgroup(s).