From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Tzung-Bi Shih <tzungbi@kernel.org>,
Brian Norris <briannorris@chromium.org>,
Julius Werner <jwerner@chromium.org>
Cc: chrome-platform@lists.linux.dev, linux-kernel@vger.kernel.org,
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: [PATCH 0/2] firmware: coreboot: store owner from modules with coreboot_driver_register()
Date: Sat, 30 Mar 2024 20:49:46 +0100 [thread overview]
Message-ID: <20240330-module-owner-coreboot-v1-0-ddba098b6dcf@linaro.org> (raw)
Moving the .owner setting code to the core this effectively fixes
missing .owner in framebuffer-coreboot, memconsole-coreboot and vpd
drivers.
Best regards,
Krzysztof
---
Krzysztof Kozlowski (2):
firmware: coreboot: store owner from modules with coreboot_driver_register()
firmware: google: cbmem: drop driver owner initialization
drivers/firmware/google/cbmem.c | 1 -
drivers/firmware/google/coreboot_table.c | 6 ++++--
drivers/firmware/google/coreboot_table.h | 6 +++++-
3 files changed, 9 insertions(+), 4 deletions(-)
---
base-commit: 7fdcff3312e16ba8d1419f8a18f465c5cc235ecf
change-id: 20240330-module-owner-coreboot-114292b6d11b
Best regards,
--
Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
next reply other threads:[~2024-03-30 19:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-30 19:49 Krzysztof Kozlowski [this message]
2024-03-30 19:49 ` [PATCH 1/2] firmware: coreboot: store owner from modules with coreboot_driver_register() 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
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=20240330-module-owner-coreboot-v1-0-ddba098b6dcf@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=briannorris@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=jwerner@chromium.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).