From: patchwork-bot+linux-soc@kernel.org
To: Sean Rhodes <sean@starlabs.systems>
Cc: soc@kernel.org
Subject: Re: [PATCH v14 0/5] coreboot CFR firmware attributes
Date: Tue, 13 Oct 2026 16:10:37 +0000 [thread overview]
Message-ID: <179190783776.417156.3721149018307710717.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <cover.1788284852.git.sean@starlabs.systems>
Hello:
This series was applied to soc/soc.git (for-next)
by Arnd Bergmann <arnd@arndb.de>:
On Tue, 1 Sep 2026 18:48:01 +0100 you wrote:
> Move the firmware attributes class helper out of platform/x86, rename the
> coreboot-table firmware driver directory from google to coreboot, and add a
> coreboot CFR firmware attributes driver.
>
> Changes in v14:
> - Rebase on current upstream master after Linux 7.3-rc1, preserving the
> intervening coreboot table bounds and CBMEM no-map changes.
> - Drop the standalone include-order cleanup. Replace the affected relative
> includes directly in the firmware attributes helper move, as requested by
> Tzung-Bi.
> - Split the DRM coreboot framebuffer dependency update from the firmware
> directory and Kconfig rename so it can receive a DRM Acked-by separately.
> - Keep the CFR driver and its runtime behavior unchanged from v13.
>
> [...]
Here is the summary with links:
- [v14,1/5] firmware: Move firmware attributes class helper
(no matching commit)
- [v14,2/5] firmware: Rename google firmware directory to coreboot
(no matching commit)
- [v14,3/5] drm/sysfb: Update coreboot framebuffer Kconfig symbol
(no matching commit)
- [v14,4/5] firmware: coreboot: Add CFR firmware attributes driver
(no matching commit)
- [v14,5/5] arm64: defconfig: Update coreboot firmware symbols
https://git.kernel.org/soc/soc/c/876108e1d248
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-10-13 16:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 17:48 [PATCH v14 0/5] coreboot CFR firmware attributes Sean Rhodes
2026-09-01 17:48 ` [PATCH v14 1/5] firmware: Move firmware attributes class helper Sean Rhodes
2026-09-02 10:14 ` Tzung-Bi Shih
2026-09-29 9:39 ` Ilpo Järvinen
2026-09-01 17:48 ` [PATCH v14 2/5] firmware: Rename google firmware directory to coreboot Sean Rhodes
2026-09-01 17:48 ` [PATCH v14 3/5] drm/sysfb: Update coreboot framebuffer Kconfig symbol Sean Rhodes
2026-09-04 9:10 ` Thomas Zimmermann
2026-09-01 17:48 ` [PATCH v14 4/5] firmware: coreboot: Add CFR firmware attributes driver Sean Rhodes
2026-09-01 17:48 ` [PATCH v14 5/5] arm64: defconfig: Update coreboot firmware symbols Sean Rhodes
2026-09-02 10:01 ` (subset) [PATCH v14 0/5] coreboot CFR firmware attributes Tzung-Bi Shih
2026-09-02 10:01 ` Sean Rhodes
2026-09-16 21:43 ` Sean Rhodes
2026-09-30 12:40 ` Tzung-Bi Shih
2026-10-13 16:10 ` patchwork-bot+linux-soc [this message]
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=179190783776.417156.3721149018307710717.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=sean@starlabs.systems \
--cc=soc@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.