From: Tzung-Bi Shih <tzungbi@kernel.org>
To: "Nícolas F. R. A. Prado" <nfraprado@collabora.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
Brian Norris <briannorris@chromium.org>,
Julius Werner <jwerner@chromium.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Nathan Chancellor <nathan@kernel.org>,
Nicolas Schier <nicolas@fjasle.eu>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@collabora.com>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
kernel@collabora.com, chrome-platform@lists.linux.dev,
linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 0/4] Allow coreboot modules to autoload and enable cbmem in the arm64 defconfig
Date: Thu, 15 Feb 2024 11:37:42 +0800 [thread overview]
Message-ID: <Zc2HBmDPJnHt0WJC@google.com> (raw)
In-Reply-To: <20240212-coreboot-mod-defconfig-v4-0-d14172676f6d@collabora.com>
On Mon, Feb 12, 2024 at 09:50:04AM -0500, Nícolas F. R. A. Prado wrote:
> This series adds the missing pieces to the coreboot bus and the module
> alias generation to allow coreboot modules to be automatically loaded
> when matching devices are detected.
>
> The configs for cbmem coreboot entries are then enabled in the arm64
> defconfig, as modules, to allow reading logs from coreboot on arm64
> Chromebooks, which is useful for debugging the boot process.
>
> [...]
>
> ---
> Nícolas F. R. A. Prado (4):
> firmware: coreboot: Generate modalias uevent for devices
> firmware: coreboot: Generate aliases for coreboot modules
> firmware: coreboot: Replace tag with id table in driver struct
> arm64: defconfig: Enable support for cbmem entries in the coreboot table
>
> arch/arm64/configs/defconfig | 3 +++
Hi Catalin and Will,
Is it OK to you if I pick the 4th patch (which touches the above files) to
chrome-platform-firmware tree for the next merge window?
> include/linux/mod_devicetable.h | 10 ++++++++++
> scripts/mod/devicetable-offsets.c | 3 +++
> scripts/mod/file2alias.c | 10 ++++++++++
Hi Masahiro,
Is it OK to you if I pick the 2nd patch (which touches the above files) to
chrome-platform-firmware tree for the next merge window?
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-02-15 3:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-12 14:50 [PATCH v4 0/4] Allow coreboot modules to autoload and enable cbmem in the arm64 defconfig Nícolas F. R. A. Prado
2024-02-12 14:50 ` [PATCH v4 1/4] firmware: coreboot: Generate modalias uevent for devices Nícolas F. R. A. Prado
2024-02-12 14:50 ` [PATCH v4 2/4] firmware: coreboot: Generate aliases for coreboot modules Nícolas F. R. A. Prado
2024-02-15 5:50 ` Masahiro Yamada
2024-02-12 14:50 ` [PATCH v4 3/4] firmware: coreboot: Replace tag with id table in driver struct Nícolas F. R. A. Prado
2024-02-12 14:50 ` [PATCH v4 4/4] arm64: defconfig: Enable support for cbmem entries in the coreboot table Nícolas F. R. A. Prado
2024-02-15 3:37 ` Tzung-Bi Shih [this message]
2024-02-15 5:52 ` [PATCH v4 0/4] Allow coreboot modules to autoload and enable cbmem in the arm64 defconfig Masahiro Yamada
2024-02-17 0:58 ` Tzung-Bi Shih
2024-03-04 13:56 ` Nícolas F. R. A. Prado
2024-03-04 14:02 ` Arnd Bergmann
2024-03-04 18:17 ` Nícolas F. R. A. Prado
2024-03-25 1:54 ` patchwork-bot+chrome-platform
2024-03-25 2:13 ` patchwork-bot+chrome-platform
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=Zc2HBmDPJnHt0WJC@google.com \
--to=tzungbi@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=angelogioacchino.delregno@collabora.com \
--cc=arnd@arndb.de \
--cc=briannorris@chromium.org \
--cc=catalin.marinas@arm.com \
--cc=chrome-platform@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=jwerner@chromium.org \
--cc=kernel@collabora.com \
--cc=linux-arm-kernel@lists.infradead.org \
--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=will@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;
as well as URLs for NNTP newsgroup(s).