From: Wolfram Sang <wsa@the-dreams.de>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: alexandre.belloni@bootlin.com, bjorn.andersson@linaro.org,
linux-arm-msm@vger.kernel.org, vkoul@kernel.org,
linux-kernel@vger.kernel.org, wsa+renesas@sang-engineering.com,
ludovic.desroches@microchip.com, agross@kernel.org,
ldewangan@nvidia.com, linux-i2c@vger.kernel.org,
linux-tegra@vger.kernel.org, thierry.reding@gmail.com,
digetx@gmail.com, jonathanh@nvidia.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/4] i2c: Use dma_request_chan() directly for channel request
Date: Thu, 14 Nov 2019 21:43:47 +0100 [thread overview]
Message-ID: <20191114204347.GB7213@kunai> (raw)
In-Reply-To: <20191113092235.30440-1-peter.ujfalusi@ti.com>
[-- Attachment #1.1: Type: text/plain, Size: 317 bytes --]
On Wed, Nov 13, 2019 at 11:22:31AM +0200, Peter Ujfalusi 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
Applied to for-next, thanks!
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-11-14 20:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 9:22 [PATCH 0/4] i2c: Use dma_request_chan() directly for channel request Peter Ujfalusi
2019-11-13 9:22 ` [PATCH 1/4] i2c: at91: " Peter Ujfalusi
2019-11-13 13:35 ` Ludovic.Desroches
2019-11-13 9:22 ` [PATCH 2/4] i2c: qup: " Peter Ujfalusi
2019-11-13 9:22 ` [PATCH 3/4] i2c: sh_mobile: " Peter Ujfalusi
2019-11-13 9:22 ` [PATCH 4/4] i2c: tegra: " Peter Ujfalusi
2019-11-14 7:05 ` Jon Hunter
2019-11-14 4:34 ` [PATCH 0/4] i2c: " Vinod Koul
2019-11-14 20:43 ` Wolfram Sang [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=20191114204347.GB7213@kunai \
--to=wsa@the-dreams.de \
--cc=agross@kernel.org \
--cc=alexandre.belloni@bootlin.com \
--cc=bjorn.andersson@linaro.org \
--cc=digetx@gmail.com \
--cc=jonathanh@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=ludovic.desroches@microchip.com \
--cc=peter.ujfalusi@ti.com \
--cc=thierry.reding@gmail.com \
--cc=vkoul@kernel.org \
--cc=wsa+renesas@sang-engineering.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;
as well as URLs for NNTP newsgroup(s).