From: Tzung-Bi Shih <tzungbi@kernel.org>
To: torvalds@linux-foundation.org
Cc: briannorris@chromium.org, jwerner@chromium.org,
groeck@chromium.org, tzungbi@kernel.org,
linux-kernel@vger.kernel.org, chrome-platform@lists.linux.dev
Subject: [GIT PULL] chrome-platform-firmware changes for v6.10
Date: Mon, 13 May 2024 12:25:42 +0800 [thread overview]
Message-ID: <ZkGWRmncTxuqnTon@google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1210 bytes --]
Hi Linus,
Please pull chrome-platform-firmware changes for v6.10.
Thanks,
TzungBi
The following changes since commit 4cece764965020c22cff7665b18a012006359095:
Linux 6.9-rc1 (2024-03-24 14:10:05 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git tags/tag-chrome-platform-firmware-for-v6.10
for you to fetch changes up to 7f20f21c22aa22e488530f66bf4fc168e427f5bd:
firmware: google: cbmem: drop driver owner initialization (2024-04-03 15:09:26 +0800)
----------------------------------------------------------------
chrome platform firmware changes for 6.10
* Improvements
- Set driver owner in the core registration so that coreboot drivers
don't need to set it individually.
----------------------------------------------------------------
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(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2024-05-13 4:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-13 4:25 Tzung-Bi Shih [this message]
2024-05-13 23:50 ` [GIT PULL] chrome-platform-firmware changes for v6.10 pr-tracker-bot
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=ZkGWRmncTxuqnTon@google.com \
--to=tzungbi@kernel.org \
--cc=briannorris@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--cc=groeck@chromium.org \
--cc=jwerner@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).