From: patchwork-bot+linux-riscv@kernel.org
To: Jisheng Zhang <jszhang@kernel.org>
Cc: linux-riscv@lists.infradead.org, guoren@kernel.org,
wefu@redhat.com, conor@kernel.org, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, paul.walmsley@sifive.com,
palmer@dabbelt.com, aou@eecs.berkeley.edu,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
dfustini@baylibre.com
Subject: Re: [PATCH v2] riscv: dts: thead: set dma-noncoherent to soc bus
Date: Sun, 12 Nov 2023 00:55:46 +0000 [thread overview]
Message-ID: <169975054638.11360.7816717973824399061.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20230912072232.2455-1-jszhang@kernel.org>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Arnd Bergmann <arnd@arndb.de>:
On Tue, 12 Sep 2023 15:22:32 +0800 you wrote:
> riscv select ARCH_DMA_DEFAULT_COHERENT by default, and th1520 isn't
> dma coherent, so set dma-noncoherent to reflect this fact.
>
> Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
> Tested-by: Drew Fustini <dfustini@baylibre.com>
> ---
>
> [...]
Here is the summary with links:
- [v2] riscv: dts: thead: set dma-noncoherent to soc bus
https://git.kernel.org/riscv/c/759426c758c7
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:[~2023-11-12 0:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 7:22 [PATCH v2] riscv: dts: thead: set dma-noncoherent to soc bus Jisheng Zhang
2023-09-12 14:48 ` Guo Ren
2023-09-12 16:27 ` Conor Dooley
2023-09-13 15:15 ` Jisheng Zhang
2023-09-13 15:44 ` Conor Dooley
2023-09-20 8:36 ` Conor Dooley
2023-09-21 9:24 ` Jisheng Zhang
2023-09-21 10:08 ` Conor Dooley
2023-10-16 17:10 ` Drew Fustini
[not found] ` <ZS6x18XEJXmB7FFL@xhacker>
2023-10-17 20:33 ` Arnd Bergmann
2023-11-12 0:55 ` patchwork-bot+linux-riscv [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=169975054638.11360.7816717973824399061.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=aou@eecs.berkeley.edu \
--cc=conor@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dfustini@baylibre.com \
--cc=guoren@kernel.org \
--cc=jszhang@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=robh+dt@kernel.org \
--cc=wefu@redhat.com \
/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