From: Jack Rosenthal <jrosenth@chromium.org>
To: Stephen Boyd <swboyd@chromium.org>
Cc: chrome-platform@lists.linux.dev, linux-kernel@vger.kernel.org,
Tzung-Bi Shih <tzungbi@kernel.org>,
Guenter Roeck <groeck@chromium.org>,
Julius Werner <jwerner@chromium.org>
Subject: Re: [PATCH v8] firmware: google: Implement cbmem in sysfs driver
Date: Mon, 15 Aug 2022 14:53:07 -0600 [thread overview]
Message-ID: <YvqyM3n48Q/0i9XZ@chromium.org> (raw)
In-Reply-To: <CAE-0n53gc=1vwZbhGUaF2EyXotMPjqoQixUMJDidcs7vLmNORQ@mail.gmail.com>
Thanks for the detailed review!
On 2022-08-09 at 20:49 -0500, Stephen Boyd wrote:
> /sys/firmware/coreboot/cbmem?
Fixed in v9.
> > +#include <linux/ctype.h>
>
> What is used from this header?
Not used, fixed in v9.
> Are all entries supposed to be writeable? Are there entries that are
> read-only?
The idea here was that we could use crossystem to update the cbmem entry
when it makes changes, however, I do see this as an odd usage of the
ABI, and in v9, I removed writing entirely and all entries are now
read-only.
If tools like crossystem need to maintain changes to this buffer, they
should either maintain that copy themselves in /run or something, or
daemonize and keep it in their process' memory.
> > + return cbmem_entry_setup(entry);
>
> Is there a reason this isn't inlined here?
cbmem_entry_setup was already a little long, so I just did this for
reading clarity. If you think it would be clearer just inlined here, I
can change it (let me know).
> Need to set .owner = THIS_MODULE unless you use
> module_coreboot_driver().
Done.
> > + if (!coreboot_kobj)
>
> cbmem_kobj?
Done.
next prev parent reply other threads:[~2022-08-16 1:09 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-06 20:48 Jack Rosenthal
2022-08-10 1:49 ` Stephen Boyd
2022-08-15 20:53 ` Jack Rosenthal [this message]
2022-08-15 22:03 ` Julius Werner
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=YvqyM3n48Q/0i9XZ@chromium.org \
--to=jrosenth@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=groeck@chromium.org \
--cc=jwerner@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=swboyd@chromium.org \
--cc=tzungbi@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
all inboxes | Powered by JetHome®