From: Vinod Koul <vkoul@kernel.org>
To: Jiasheng Jiang <jiasheng@iscas.ac.cn>
Cc: geert@linux-m68k.org, yoshihiro.shimoda.uh@renesas.com,
laurent.pinchart@ideasonboard.com,
wsa+renesas@sang-engineering.com, zou_wei@huawei.com,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert+renesas@glider.be>
Subject: Re: [PATCH] dmaengine: sh: rcar-dmac: Check for error num after dma_set_max_seg_size
Date: Tue, 15 Feb 2022 11:00:21 +0530 [thread overview]
Message-ID: <Ygs6beVaf5M+fLkK@matsya> (raw)
In-Reply-To: <20220111011239.452837-1-jiasheng@iscas.ac.cn>
On 11-01-22, 09:12, Jiasheng Jiang wrote:
> As the possible failure of the dma_set_max_seg_size(), it should be
> better to check the return value of the dma_set_max_seg_size().
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2022-02-15 5:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 1:12 [PATCH] dmaengine: sh: rcar-dmac: Check for error num after dma_set_max_seg_size Jiasheng Jiang
2022-01-11 9:42 ` Geert Uytterhoeven
2022-02-15 5:30 ` Vinod Koul [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=Ygs6beVaf5M+fLkK@matsya \
--to=vkoul@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=geert@linux-m68k.org \
--cc=jiasheng@iscas.ac.cn \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=wsa+renesas@sang-engineering.com \
--cc=yoshihiro.shimoda.uh@renesas.com \
--cc=zou_wei@huawei.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