public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Brian Norris <briannorris@chromium.org>
Cc: "Andy Shevchenko" <andriy.shevchenko@linux.intel.com>,
	"Nícolas F. R. A. Prado" <nfraprado@collabora.com>,
	"Tzung-Bi Shih" <tzungbi@kernel.org>,
	kernel@collabora.com,
	"AngeloGioacchino Del Regno"
	<angelogioacchino.delregno@collabora.com>,
	chrome-platform@lists.linux.dev,
	"Abhijit Gangurde" <abhijit.gangurde@amd.com>,
	"Masahiro Yamada" <masahiroy@kernel.org>,
	"Nathan Chancellor" <nathan@kernel.org>,
	"Nicolas Schier" <nicolas@fjasle.eu>,
	"Nipun Gupta" <nipun.gupta@amd.com>,
	"Pieter Jansen van Vuuren" <pieter.jansen-van-vuuren@amd.com>,
	"Umang Jain" <umang.jain@ideasonboard.com>,
	linux-kbuild@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/7] firmware: coreboot: Generate aliases for coreboot modules
Date: Tue, 30 Jan 2024 16:23:02 -0800	[thread overview]
Message-ID: <2024013012-gully-goofy-2a55@gregkh> (raw)
In-Reply-To: <CA+ASDXM-m6U+JFvBSSHMxAf8Ct-T-pL8tmcHxHQjepdRFR-s1w@mail.gmail.com>

On Tue, Jan 30, 2024 at 04:01:57PM -0800, Brian Norris wrote:
> On Tue, Jan 30, 2024 at 3:51 PM Greg Kroah-Hartman
> <gregkh@linuxfoundation.org> wrote:
> > On Tue, Jan 23, 2024 at 02:06:14PM -0800, Brian Norris wrote:
> > > "Don't you want to have a driver data or so associated with this?"
> ...
> > But why limit yourself to 32bits now?  Why not make it 64?  It is going
> > to be sent to userspace, so you have to be very careful about it.
> 
> Is that question related to the question I pasted/replied to, about
> driver data? Or a new topic? Sorry if I'm misunderstanding.

Same question, driver data, you make it 32 bits.

> Anyway, for the size of the tag field: I don't have a strong opinion.
> But FWIW, they're coming from this project:
> 
> https://review.coreboot.org/plugins/gitiles/coreboot/+/269b23280f928510bcadd23182294e5b9dad11ec/payloads/libpayload/include/coreboot_tables.h#36
> 
> As you can see there, we're extremely far from exhausting 16 bits, let alone 32.

We've run into running out of bits in other subsystems before, it's
"free" now, just be safe and make it 64 like I think Andy is suggesting.

thanks,

greg k-h

  reply	other threads:[~2024-01-31  0:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-12 13:18 [PATCH v2 0/7] Allow coreboot modules to autoload and enable cbmem in the arm64 defconfig Nícolas F. R. A. Prado
2024-01-12 13:18 ` [PATCH v2 1/7] firmware: coreboot: Generate modalias uevent for devices Nícolas F. R. A. Prado
2024-01-12 13:18 ` [PATCH v2 2/7] firmware: coreboot: Generate aliases for coreboot modules Nícolas F. R. A. Prado
2024-01-14 17:09   ` Andy Shevchenko
2024-01-23 22:06     ` Brian Norris
2024-01-30 23:51       ` Greg Kroah-Hartman
2024-01-31  0:01         ` Brian Norris
2024-01-31  0:23           ` Greg Kroah-Hartman [this message]
2024-02-01 22:45             ` Nícolas F. R. A. Prado
2024-02-02  2:21               ` Greg Kroah-Hartman
2024-02-06 20:53                 ` Nícolas F. R. A. Prado
2024-01-12 13:18 ` [PATCH v2 3/7] firmware: google: cbmem: Add to module device table Nícolas F. R. A. Prado
2024-01-12 13:18 ` [PATCH v2 4/7] firmware: google: vpd: " Nícolas F. R. A. Prado
2024-01-12 13:18 ` [PATCH v2 5/7] firmware: google: memconsole: " Nícolas F. R. A. Prado
2024-01-12 13:18 ` [PATCH v2 6/7] firmware: google: framebuffer: " Nícolas F. R. A. Prado
2024-01-12 13:18 ` [PATCH v2 7/7] arm64: defconfig: Enable support for cbmem entries in the coreboot table Nícolas F. R. A. Prado
2024-01-17 10:29 ` [PATCH v2 0/7] Allow coreboot modules to autoload and enable cbmem in the arm64 defconfig AngeloGioacchino Del Regno

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=2024013012-gully-goofy-2a55@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=abhijit.gangurde@amd.com \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=briannorris@chromium.org \
    --cc=chrome-platform@lists.linux.dev \
    --cc=kernel@collabora.com \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=masahiroy@kernel.org \
    --cc=nathan@kernel.org \
    --cc=nfraprado@collabora.com \
    --cc=nicolas@fjasle.eu \
    --cc=nipun.gupta@amd.com \
    --cc=pieter.jansen-van-vuuren@amd.com \
    --cc=tzungbi@kernel.org \
    --cc=umang.jain@ideasonboard.com \
    /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