From: patchwork-bot+chrome-platform@kernel.org
To: Brian Norris <briannorris@chromium.org>
Cc: gregkh@linuxfoundation.org, bleung@chromium.org,
chrome-platform@lists.linux.dev, linux-kernel@vger.kernel.org,
samuel@sholland.org, jwerner@chromium.org, swboyd@chromium.org,
linux@roeck-us.net, stable@vger.kernel.org
Subject: Re: [PATCH] firmware: coreboot: Register bus in module init
Date: Mon, 26 Dec 2022 03:41:31 +0000 [thread overview]
Message-ID: <167202609138.9518.12964660345062034201.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20221019180934.1.If29e167d8a4771b0bf4a39c89c6946ed764817b9@changeid>
Hello:
This patch was applied to chrome-platform/linux.git (for-next)
by Greg Kroah-Hartman <gregkh@linuxfoundation.org>:
On Wed, 19 Oct 2022 18:10:53 -0700 you wrote:
> The coreboot_table driver registers a coreboot bus while probing a
> "coreboot_table" device representing the coreboot table memory region.
> Probing this device (i.e., registering the bus) is a dependency for the
> module_init() functions of any driver for this bus (e.g.,
> memconsole-coreboot.c / memconsole_driver_init()).
>
> With synchronous probe, this dependency works OK, as the link order in
> the Makefile ensures coreboot_table_driver_init() (and thus,
> coreboot_table_probe()) completes before a coreboot device driver tries
> to add itself to the bus.
>
> [...]
Here is the summary with links:
- firmware: coreboot: Register bus in module init
https://git.kernel.org/chrome-platform/c/65946690ed8d
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2022-12-26 3:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-20 1:10 [PATCH] firmware: coreboot: Register bus in module init Brian Norris
2022-10-20 1:20 ` Guenter Roeck
2022-10-22 0:28 ` Brian Norris
2022-10-21 0:04 ` Stephen Boyd
2022-12-26 3:32 ` patchwork-bot+chrome-platform
2022-12-26 3:41 ` patchwork-bot+chrome-platform [this message]
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=167202609138.9518.12964660345062034201.git-patchwork-notify@kernel.org \
--to=patchwork-bot+chrome-platform@kernel.org \
--cc=bleung@chromium.org \
--cc=briannorris@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=gregkh@linuxfoundation.org \
--cc=jwerner@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=samuel@sholland.org \
--cc=stable@vger.kernel.org \
--cc=swboyd@chromium.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