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.11
Date: Mon, 15 Jul 2024 12:15:45 +0800 [thread overview]
Message-ID: <ZpSicQDtkyR5r4vF@tzungbi-laptop> (raw)
[-- Attachment #1: Type: text/plain, Size: 1288 bytes --]
Hi Linus,
Please pull chrome-platform-firmware changes for v6.11.
Thanks,
TzungBi
------
The following changes since commit 1613e604df0cd359cf2a7fbd9be7a0bcfacfabd0:
Linux 6.10-rc1 (2024-05-26 15:20:12 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/chrome-platform/linux.git tags/tag-chrome-platform-firmware-for-v6.11
for you to fetch changes up to fc2c1d716d4a879dd52c612ea19a7f994f08748d:
firmware: google: add missing MODULE_DESCRIPTION() macros (2024-06-11 03:34:05 +0000)
----------------------------------------------------------------
chrome platform firmware changes for 6.11
* Minor cleanups.
----------------------------------------------------------------
Jeff Johnson (1):
firmware: google: add missing MODULE_DESCRIPTION() macros
drivers/firmware/google/cbmem.c | 1 +
drivers/firmware/google/coreboot_table.c | 1 +
drivers/firmware/google/framebuffer-coreboot.c | 1 +
drivers/firmware/google/gsmi.c | 1 +
drivers/firmware/google/memconsole-coreboot.c | 1 +
drivers/firmware/google/memconsole-x86-legacy.c | 1 +
drivers/firmware/google/memconsole.c | 1 +
drivers/firmware/google/vpd.c | 1 +
8 files changed, 8 insertions(+)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2024-07-15 4:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 4:15 Tzung-Bi Shih [this message]
2024-07-16 0:51 ` 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=ZpSicQDtkyR5r4vF@tzungbi-laptop \
--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
all inboxes | Powered by JetHome®