From: patchwork-bot+linux-soc@kernel.org
To: Mathew McBride <matt@traverse.com.au>
Cc: soc@kernel.org
Subject: Re: [PATCH 1/1 RESEND] soc: fsl: select FSL_GUTS driver for DPIO
Date: Fri, 02 Sep 2022 11:00:17 +0000 [thread overview]
Message-ID: <166211641797.12856.14700760201274401613.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20220901052149.23873-2-matt@traverse.com.au>
Hello:
This patch was applied to soc/soc.git (arm/fixes)
by Arnd Bergmann <arnd@arndb.de>:
On Thu, 1 Sep 2022 05:21:49 +0000 you wrote:
> The soc/fsl/dpio driver will perform a soc_device_match()
> to determine the optimal cache settings for a given CPU core.
>
> If FSL_GUTS is not enabled, this search will fail and
> the driver will not configure cache stashing for the given
> DPIO, and a string of "unknown SoC" messages will appear:
>
> [...]
Here is the summary with links:
- [1/1,RESEND] soc: fsl: select FSL_GUTS driver for DPIO
https://git.kernel.org/soc/soc/c/9a472613f5bc
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:[~2022-09-02 11:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-20 4:32 [PATCH] soc: fsl: select FSL_GUTS driver for DPIO Mathew McBride
2022-06-20 4:32 ` Mathew McBride
2022-06-23 15:24 ` Ioana Ciornei
2022-06-23 15:24 ` Ioana Ciornei
2022-09-01 5:21 ` [PATCH 0/1 RESEND] update Kconfig for DPIO to select FSL_GUTS Mathew McBride
2022-09-01 5:21 ` Mathew McBride
2022-09-01 5:21 ` [PATCH 1/1 RESEND] soc: fsl: select FSL_GUTS driver for DPIO Mathew McBride
2022-09-01 5:21 ` Mathew McBride
2022-09-02 11:00 ` 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=166211641797.12856.14700760201274401613.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-soc@kernel.org \
--cc=matt@traverse.com.au \
--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.