From: Tzung-Bi Shih <tzungbi@kernel.org>
To: torvalds@linux-foundation.org
Cc: briannorris@chromium.org, jwerner@chromium.org,
tzungbi@kernel.org, linux-kernel@vger.kernel.org,
chrome-platform@lists.linux.dev
Subject: [GIT PULL] chrome-platform-firmware updates for v7.3
Date: Mon, 17 Aug 2026 03:13:01 +0000 [thread overview]
Message-ID: <aoJ8Pbv35-mKIHun@google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1218 bytes --]
Hi Linus,
Please pull chrome-platform-firmware updates for Linux v7.3.
Thanks,
Tzung-Bi
------
The following changes since commit 1590cf0329716306e948a8fc29f1d3ee87d3989f:
Linux 7.2-rc4 (2026-07-19 13:54:41 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git tags/chrome-platform-firmware-v7.3
for you to fetch changes up to a58a57a1076f8c5dae0327e3710899478c3be901:
firmware: coreboot: Validate table bounds (2026-08-03 03:00:21 +0000)
----------------------------------------------------------------
chrome-platform-firmware: Updates for v7.3
* Fixes
- Don't map no-map memory regions for CBMEM entries.
- Check bound of coreboot table entries.
* Cleanups
- Fix typo in docs.
----------------------------------------------------------------
Laxman Acharya Padhya (1):
firmware: coreboot: Validate table bounds
Manuel Ebner (1):
docs: ABI: testing: Fix typo
Yidi Lin (1):
firmware: coreboot: Skip no-map CBMEM entries
Documentation/ABI/testing/sysfs-firmware-gsmi | 2 +-
drivers/firmware/google/coreboot_table.c | 43 ++++++++++++++++++++++-----
2 files changed, 37 insertions(+), 8 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
reply other threads:[~2026-08-17 3:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=aoJ8Pbv35-mKIHun@google.com \
--to=tzungbi@kernel.org \
--cc=briannorris@chromium.org \
--cc=chrome-platform@lists.linux.dev \
--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