From: patchwork-bot+chrome-platform@kernel.org
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: tzungbi@kernel.org, briannorris@chromium.org,
jwerner@chromium.org, chrome-platform@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/2] firmware: coreboot: store owner from modules with coreboot_driver_register()
Date: Mon, 27 May 2024 03:07:05 +0000 [thread overview]
Message-ID: <171677922587.1901.3423676427961660678.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240330-module-owner-coreboot-v1-0-ddba098b6dcf@linaro.org>
Hello:
This series was applied to chrome-platform/linux.git (for-next)
by Tzung-Bi Shih <tzungbi@kernel.org>:
On Sat, 30 Mar 2024 20:49:46 +0100 you wrote:
> Moving the .owner setting code to the core this effectively fixes
> missing .owner in framebuffer-coreboot, memconsole-coreboot and vpd
> drivers.
>
> Best regards,
> Krzysztof
>
> [...]
Here is the summary with links:
- [1/2] firmware: coreboot: store owner from modules with coreboot_driver_register()
https://git.kernel.org/chrome-platform/c/46c6685e7e88
- [2/2] firmware: google: cbmem: drop driver owner initialization
https://git.kernel.org/chrome-platform/c/7f20f21c22aa
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:[~2024-05-27 3:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-30 19:49 [PATCH 0/2] firmware: coreboot: store owner from modules with coreboot_driver_register() Krzysztof Kozlowski
2024-03-30 19:49 ` [PATCH 1/2] " Krzysztof Kozlowski
2024-03-30 19:49 ` [PATCH 2/2] firmware: google: cbmem: drop driver owner initialization Krzysztof Kozlowski
2024-04-24 6:40 ` [PATCH 0/2] firmware: coreboot: store owner from modules with coreboot_driver_register() Krzysztof Kozlowski
2024-04-24 8:43 ` Tzung-Bi Shih
2024-05-27 2:55 ` patchwork-bot+chrome-platform
2024-05-27 3:07 ` 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=171677922587.1901.3423676427961660678.git-patchwork-notify@kernel.org \
--to=patchwork-bot+chrome-platform@kernel.org \
--cc=briannorris@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=jwerner@chromium.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.