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 changes for v6.13
Date: Mon, 18 Nov 2024 00:32:38 +0000 [thread overview]
Message-ID: <ZzqLJjQwz0adE120@google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1392 bytes --]
The following changes since commit 9852d85ec9d492ebef56dc5f229416c925758edc:
Linux 6.12-rc1 (2024-09-29 15:06:19 -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-for-6.13
for you to fetch changes up to 32b0901e141f6d4cf49d820b53eb09b88b1f72f7:
firmware: google: Unregister driver_info on failure (2024-10-15 22:51:24 +0000)
----------------------------------------------------------------
chrome platform firmware changes for 6.13
* Fixes
- Do not double register "simple-framebuffer" platform device if
Generic System Framebuffers (sysfb) already did that.
- Fix a missing of unregistering platform driver in error handling
path.
----------------------------------------------------------------
Javier Martinez Canillas (2):
firmware: sysfb: Add a sysfb_handles_screen_info() helper function
firmware: coreboot: Don't register a pdev if screen_info data is present
Yuan Can (1):
firmware: google: Unregister driver_info on failure
drivers/firmware/google/framebuffer-coreboot.c | 14 ++++++++++++++
drivers/firmware/google/gsmi.c | 6 ++++--
drivers/firmware/sysfb.c | 19 +++++++++++++++++++
include/linux/sysfb.h | 7 +++++++
4 files changed, 44 insertions(+), 2 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2024-11-18 0:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 0:32 Tzung-Bi Shih [this message]
2024-11-19 19:06 ` [GIT PULL] chrome-platform-firmware changes for v6.13 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=ZzqLJjQwz0adE120@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