Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Subject: Re: [PATCH] firmware: coreboot: Register bus in module init
From:   patchwork-bot+chrome-platform@kernel.org
Message-Id: <167202609138.9518.12964660345062034201.git-patchwork-notify@kernel.org>
Date:   Mon, 26 Dec 2022 03:41:31 +0000
References: <20221019180934.1.If29e167d8a4771b0bf4a39c89c6946ed764817b9@changeid>
In-Reply-To: <20221019180934.1.If29e167d8a4771b0bf4a39c89c6946ed764817b9@changeid>
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
Precedence: bulk

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