From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Jonathan Cameron <jic23@kernel.org>,
Vinod Koul <vkoul@kernel.org>, <knaack.h@gmx.de>,
<lars@metafoo.de>, <linux-iio@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <pmeerw@pmeerw.net>
Subject: Re: [PATCH] iio: buffer-dmaengine: Use dma_request_chan() directly for channel request
Date: Wed, 8 Jan 2020 14:21:54 +0000 [thread overview]
Message-ID: <20200108142154.00003ccf@Huawei.com> (raw)
In-Reply-To: <4d4c4338-b028-e28b-a603-323eadebd261@ti.com>
On Tue, 7 Jan 2020 14:19:43 +0200
Peter Ujfalusi <peter.ujfalusi@ti.com> wrote:
> Jonathan,
>
> On 16/11/2019 18.22, Jonathan Cameron wrote:
> > On Thu, 14 Nov 2019 10:03:18 +0530
> > Vinod Koul <vkoul@kernel.org> wrote:
> >
> >> On 13-11-19, 11:24, Peter Ujfalusi wrote:
> >>> dma_request_slave_channel_reason() is:
> >>> #define dma_request_slave_channel_reason(dev, name) \
> >>> dma_request_chan(dev, name)
> >>
> >> Reviewed-by: Vinod Koul <vkoul@kernel.org>
> >>
> >
> > Applied to the togreg branch of iio.git and pushed out as testing
> > for the autobuilders to play with it.
>
> The sole user in mainline for dma_request_slave_channel_reason() is
> industrialio-buffer-dmaengine.c (since v5.5-rc1, 5.4 had 36 users).
>
> Are you planning to queue this patch for 5.6 (not sure if it could be
> sent to -rc6) so I can retire it from the dmaengine.h?
It's queued up for the 5.6 merge window.
Jonathan
>
> Regards,
> - Péter
>
> >
> > Thanks,
> >
> > Jonathan
> >
>
> Texas Instruments Finland Oy, Porkkalankatu 22, 00180 Helsinki.
> Y-tunnus/Business ID: 0615521-4. Kotipaikka/Domicile: Helsinki
prev parent reply other threads:[~2020-01-08 14:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 9:24 [PATCH] iio: buffer-dmaengine: Use dma_request_chan() directly for channel request Peter Ujfalusi
2019-11-14 4:33 ` Vinod Koul
2019-11-16 16:22 ` Jonathan Cameron
2020-01-07 12:19 ` Peter Ujfalusi
2020-01-08 14:21 ` Jonathan Cameron [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=20200108142154.00003ccf@Huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=jic23@kernel.org \
--cc=knaack.h@gmx.de \
--cc=lars@metafoo.de \
--cc=linux-iio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peter.ujfalusi@ti.com \
--cc=pmeerw@pmeerw.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.