From: patchwork-bot+linux-riscv@kernel.org
To: Guenter Roeck <linux@roeck-us.net>
Cc: linux-riscv@lists.infradead.org, ulf.hansson@linaro.org,
paul.walmsley@sifive.com, samuel.holland@sifive.com,
linux-mmc@vger.kernel.org, linux-kernel@vger.kernel.org,
hch@lst.de, robin.murphy@arm.com
Subject: Re: [PATCH] mmc: core: Only set maximum DMA segment size if DMA is supported
Date: Tue, 12 Nov 2024 22:53:14 +0000 [thread overview]
Message-ID: <173145199424.701548.5612261824540957185.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240924210123.2288529-1-linux@roeck-us.net>
Hello:
This patch was applied to riscv/linux.git (fixes)
by Ulf Hansson <ulf.hansson@linaro.org>:
On Tue, 24 Sep 2024 14:01:23 -0700 you wrote:
> Since upstream commit 334304ac2bac ("dma-mapping: don't return errors
> from dma_set_max_seg_size") calling dma_set_max_seg_size() on a device
> not supporting DMA results in a warning traceback. This is seen when
> booting the sifive_u machine from SD. The underlying SPI controller
> (sifive,spi0 compatible) explicitly sets dma_mask to NULL.
>
> Avoid the backtrace by only calling dma_set_max_seg_size() if DMA is
> supported.
>
> [...]
Here is the summary with links:
- mmc: core: Only set maximum DMA segment size if DMA is supported
https://git.kernel.org/riscv/c/c26339faed11
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:[~2024-11-12 22:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-24 21:01 [PATCH] mmc: core: Only set maximum DMA segment size if DMA is supported Guenter Roeck
2024-09-26 7:35 ` Christoph Hellwig
2024-09-26 15:56 ` Robin Murphy
2024-10-01 14:51 ` Geert Uytterhoeven
2024-10-02 23:36 ` Ulf Hansson
2024-11-12 22:53 ` 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=173145199424.701548.5612261824540957185.git-patchwork-notify@kernel.org \
--to=patchwork-bot+linux-riscv@kernel.org \
--cc=hch@lst.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@roeck-us.net \
--cc=paul.walmsley@sifive.com \
--cc=robin.murphy@arm.com \
--cc=samuel.holland@sifive.com \
--cc=ulf.hansson@linaro.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