From: Vinod Koul <vkoul@kernel.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: dmaengine@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/9] dmaengine: Tidy up dma_parms
Date: Fri, 11 Sep 2020 17:42:58 +0530 [thread overview]
Message-ID: <20200911121258.GZ77521@vkoul-mobl> (raw)
In-Reply-To: <cover.1599164692.git.robin.murphy@arm.com>
On 03-09-20, 21:25, Robin Murphy wrote:
> Just a bit of trivial housekeeping now that it's no longer necessary for
> platform and AMBA devices to allocate their own dma_parms. Feel free to
> squash patches if desired.
Applied all, thanks
>
> I have no idea why I'm spending my own Thursday evening on this, but
> apparently the itch has to be scratched :)
And looking at diffstat and good itch scratched :-)
> 9 files changed, 24 deletions(-)
--
~Vinod
_______________________________________________
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:[~2020-09-11 12:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-03 20:25 [PATCH 0/9] dmaengine: Tidy up dma_parms Robin Murphy
2020-09-03 20:25 ` [PATCH 1/9] dmaengine: axi-dmac: Drop local dma_parms Robin Murphy
2020-09-03 20:25 ` [PATCH 2/9] dmaengine: bcm2835: " Robin Murphy
2020-09-03 20:25 ` [PATCH 3/9] dmaengine: imx-dma: " Robin Murphy
2020-09-03 20:25 ` [PATCH 4/9] dmaengine: imx-sdma: " Robin Murphy
2020-09-03 20:25 ` [PATCH 5/9] dmaengine: mxs: " Robin Murphy
2020-09-03 20:25 ` [PATCH 6/9] dmaengine: rcar-dmac: " Robin Murphy
2020-09-03 20:25 ` [PATCH 7/9] dmaengine: ste_dma40: " Robin Murphy
2020-09-03 20:25 ` [PATCH 8/9] dmaengine: qcom: bam_dma: " Robin Murphy
2020-09-03 20:25 ` [PATCH 9/9] dmaengine: pl330: " Robin Murphy
2020-09-11 12:12 ` 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=20200911121258.GZ77521@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=robin.murphy@arm.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