From: Ulf Hansson <ulf.hansson@linaro.org>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Ludovic Desroches <ludovic.desroches@microchip.com>,
vkoul@kernel.org,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
Linux ARM <linux-arm-kernel@lists.infradead.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Nicolas Ferre <nicolas.ferre@microchip.com>,
Alexandre Belloni <alexandre.belloni@bootlin.com>
Subject: Re: [PATCH 0/2] mms: Use dma_request_chan() directly for channel request
Date: Thu, 14 Nov 2019 13:53:30 +0100 [thread overview]
Message-ID: <CAPDyKFp15ZMq1f_xwrPSRbhU4M4SXhRzigA9-QMNBGSZj-YtJA@mail.gmail.com> (raw)
In-Reply-To: <20191113093616.32474-1-peter.ujfalusi@ti.com>
On Wed, 13 Nov 2019 at 10:35, Peter Ujfalusi <peter.ujfalusi@ti.com> wrote:
>
> Hi,
>
> I'm going through the tree to remove dma_request_slave_channel_reason() as it
> is just:
> #define dma_request_slave_channel_reason(dev, name) \
> dma_request_chan(dev, name)
>
> Regards,
> Peter
> ---
> Peter Ujfalusi (2):
> mmc: atmel-mci: Use dma_request_chan() directly for channel request
> mmc: moxart: Use dma_request_chan() directly for channel request
>
> drivers/mmc/host/atmel-mci.c | 3 +--
> drivers/mmc/host/moxart-mmc.c | 4 ++--
> 2 files changed, 3 insertions(+), 4 deletions(-)
Applied for next, thanks!
Kind regards
Uffe
prev parent reply other threads:[~2019-11-14 12:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 9:36 [PATCH 0/2] mms: Use dma_request_chan() directly for channel request Peter Ujfalusi
2019-11-13 9:36 ` [PATCH 1/2] mmc: atmel-mci: " Peter Ujfalusi
2019-11-13 13:34 ` Ludovic.Desroches
2019-11-13 9:36 ` [PATCH 2/2] mmc: moxart: " Peter Ujfalusi
2019-11-14 4:33 ` [PATCH 0/2] mms: " Vinod Koul
2019-11-14 12:53 ` Ulf Hansson [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=CAPDyKFp15ZMq1f_xwrPSRbhU4M4SXhRzigA9-QMNBGSZj-YtJA@mail.gmail.com \
--to=ulf.hansson@linaro.org \
--cc=alexandre.belloni@bootlin.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=nicolas.ferre@microchip.com \
--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).