From: Vinod Koul <vkoul@kernel.org>
To: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Cc: Dan Carpenter <dan.carpenter@oracle.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
dmaengine@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dmaengine: uniphier-xdmac: Use readl_poll_timeout_atomic() in atomic state
Date: Tue, 27 Jul 2021 18:15:49 +0530 [thread overview]
Message-ID: <YP///aRr+/eR5viL@matsya> (raw)
In-Reply-To: <1627364852-28432-1-git-send-email-hayashi.kunihiko@socionext.com>
On 27-07-21, 14:47, Kunihiko Hayashi wrote:
> The function uniphier_xdmac_chan_stop() is only called in atomic state.
> Should use readl_poll_timeout_atomic() there instead of
> readl_poll_timeout().
Applied, thanks
--
~Vinod
prev parent reply other threads:[~2021-07-27 12:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-27 5:47 [PATCH] dmaengine: uniphier-xdmac: Use readl_poll_timeout_atomic() in atomic state Kunihiko Hayashi
2021-07-27 12:45 ` 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=YP///aRr+/eR5viL@matsya \
--to=vkoul@kernel.org \
--cc=dan.carpenter@oracle.com \
--cc=dmaengine@vger.kernel.org \
--cc=hayashi.kunihiko@socionext.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhiramat@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;
as well as URLs for NNTP newsgroup(s).