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 fixes for v7.4-rc2
Date: Thu, 5 Nov 2026 04:50:52 +0000 [thread overview]
Message-ID: <auwLLFIY6FBdB1H0@google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1296 bytes --]
Hi Linus,
Please pull chrome-platform-firmware fixes for Linux v7.4-rc2.
Thanks,
Tzung-Bi
------
The following changes since commit f2e05ce9763feb1dd7da15afd2cc61df227ee85a:
firmware: coreboot: Add CFR firmware attributes driver (2026-09-30 20:34:13 +0800)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git tags/chrome-platform-firmware-fixes-v7.4-rc2
for you to fetch changes up to 2433db2af8e1482a3a50b8cefaf25cf7e4a9374d:
firmware: coreboot: Fix CFR error-pointer handling warning (2026-11-02 03:11:53 +0000)
----------------------------------------------------------------
chrome-platform-firmware: Fixes for v7.4-rc2
- Don't skip CBMEM entries outside of known memory resources.
- Fix a Coccinelle warning for error-pointer handling in coreboot-cfr.
----------------------------------------------------------------
Michał Kopeć (1):
firmware: coreboot: Don't skip CBMEM entries outside of known memory
Sean Rhodes (1):
firmware: coreboot: Fix CFR error-pointer handling warning
drivers/firmware/coreboot/coreboot-cfr.c | 2 +-
drivers/firmware/coreboot/coreboot_table.c | 42 ++++++++++++++++++------------
2 files changed, 26 insertions(+), 18 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
reply other threads:[~2026-11-05 4:50 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=auwLLFIY6FBdB1H0@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
all inboxes | Powered by JetHome®