From: Bin Liu <b-liu@ti.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: <gregkh@linuxfoundation.org>, <vkoul@kernel.org>,
<linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] usb: musb/ux500: Use dma_request_chan() instead dma_request_slave_channel()
Date: Tue, 17 Dec 2019 12:51:39 -0600 [thread overview]
Message-ID: <20191217185139.GE14499@iaqt7> (raw)
In-Reply-To: <20191217110030.26887-1-peter.ujfalusi@ti.com>
On Tue, Dec 17, 2019 at 01:00:30PM +0200, Peter Ujfalusi wrote:
> dma_request_slave_channel() is a wrapper on top of dma_request_chan()
> eating up the error code.
>
> Signed-off-by: Peter Ujfalusi <peter.ujfalusi@ti.com>
> ---
Applied. Thanks.
-Bin.
prev parent reply other threads:[~2019-12-17 18:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-17 11:00 [PATCH] usb: musb/ux500: Use dma_request_chan() instead dma_request_slave_channel() Peter Ujfalusi
2019-12-17 18:51 ` Bin Liu [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=20191217185139.GE14499@iaqt7 \
--to=b-liu@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=vkoul@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).