From: Conor Dooley <conor@kernel.org>
To: soc@kernel.org
Cc: conor@kernel.org, jonathan.cameron@huawei.com,
linux-kernel@vger.kernel.org
Subject: [GIT PULL] standalone cache drivers for v7.2
Date: Mon, 8 Jun 2026 11:56:45 +0100 [thread overview]
Message-ID: <20260608-retool-automatic-2e55911639f9@spud> (raw)
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
Hey folks,
Just a single two-liner patch here on the cache front.
A new driver popped up in the last few weeks but isn't ready for this
cycle.
Cheers,
Conor.
The following changes since commit 254f49634ee16a731174d2ae34bc50bd5f45e731:
Linux 7.1-rc1 (2026-04-26 14:19:00 -0700)
are available in the Git repository at:
https://git.kernel.org/pub/scm/linux/kernel/git/conor/linux.git/ cache-for-v7.2
for you to fetch changes up to 8e2501e1494c8d27f62eb8d36bba5af465f48962:
cache: sifive_ccache: Add StarFive JH7110 SoC support (2026-05-21 11:12:00 +0100)
----------------------------------------------------------------
standalone cache drivers for v7.2
SiFive ccache:
Add the Starfive JH7110 to the list of devices that need the
non-standard cache ops, because the GPU appears to be DMA non-coherent
unlike other peripherals.
Signed-off-by: Conor Dooley <conor.dooley@microchip.com>
----------------------------------------------------------------
Dominique Belhachemi (1):
cache: sifive_ccache: Add StarFive JH7110 SoC support
drivers/cache/sifive_ccache.c | 2 ++
1 file changed, 2 insertions(+)
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next reply other threads:[~2026-06-08 10:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-08 10:56 Conor Dooley [this message]
2026-06-09 16:40 ` [GIT PULL] standalone cache drivers for v7.2 patchwork-bot+linux-soc
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=20260608-retool-automatic-2e55911639f9@spud \
--to=conor@kernel.org \
--cc=jonathan.cameron@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox