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 v6.14
Date: Mon, 20 Jan 2025 01:56:51 +0000 [thread overview]
Message-ID: <Z42tY9rGfqes47SM@google.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1350 bytes --]
Hi Linus,
Please pull chrome-platform-firmware updates for v6.14.
Thanks,
Tzung-Bi
The following changes since commit 40384c840ea1944d7c5a392e8975ed088ecf0b37:
Linux 6.13-rc1 (2024-12-01 14:28:56 -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-v6.14
for you to fetch changes up to 7543d5702c2cfe0e8e8bc8bf4fe8cd44f08d6d39:
firmware: google: vpd: Use const 'struct bin_attribute' callback (2024-12-17 03:59:31 +0000)
----------------------------------------------------------------
chrome-platform-firmware: Updates for v6.14
* Cleanups
- Constify 'struct bin_attribute'.
----------------------------------------------------------------
Thomas Weißschuh (4):
firmware: google: cbmem: Constify 'struct bin_attribute'
firmware: google: gsmi: Constify 'struct bin_attribute'
firmware: google: memconsole: Use const 'struct bin_attribute' callback
firmware: google: vpd: Use const 'struct bin_attribute' callback
drivers/firmware/google/cbmem.c | 10 +++++-----
drivers/firmware/google/gsmi.c | 6 +++---
drivers/firmware/google/memconsole.c | 4 ++--
drivers/firmware/google/vpd.c | 8 ++++----
4 files changed, 14 insertions(+), 14 deletions(-)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2025-01-20 1:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-20 1:56 Tzung-Bi Shih [this message]
2025-01-22 4:15 ` [GIT PULL] chrome-platform-firmware updates for v6.14 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=Z42tY9rGfqes47SM@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