From: Geert Uytterhoeven <geert+renesas@glider.be>
To: Vinod Koul <vkoul@kernel.org>
Cc: Dan Williams <dan.j.williams@intel.com>,
Lars-Peter Clausen <lars@metafoo.de>,
Matt Porter <mporter@konsulko.com>, Arnd Bergmann <arnd@arndb.de>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
Geert Uytterhoeven <geert@linux-m68k.org>
Subject: [PATCH v2 0/3] dmaengine: Miscellaneous cleanups
Date: Tue, 21 Jan 2020 10:33:08 +0100 [thread overview]
Message-ID: <20200121093311.28639-1-geert+renesas@glider.be> (raw)
From: Geert Uytterhoeven <geert@linux-m68k.org>
Hi Vinod,
This patch series contains a few miscellaneous cleanups for the DMA
engine code and API.
Changes compared to v1:
- Add Acked-by,
- Rebase on top of today's slave-dma/next.
Thanks!
Geert Uytterhoeven (3):
dmaengine: Remove dma_device_satisfies_mask() wrapper
dmaengine: Remove dma_request_slave_channel_compat() wrapper
dmaengine: Move dma_get_{,any_}slave_channel() to private dmaengine.h
drivers/dma/dmaengine.c | 9 +++------
drivers/dma/dmaengine.h | 3 +++
drivers/dma/of-dma.c | 2 ++
include/linux/dmaengine.h | 8 ++------
4 files changed, 10 insertions(+), 12 deletions(-)
--
2.17.1
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next reply other threads:[~2020-01-21 9:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-21 9:33 Geert Uytterhoeven [this message]
2020-01-21 9:33 ` [PATCH v2 1/3] dmaengine: Remove dma_device_satisfies_mask() wrapper Geert Uytterhoeven
2020-01-21 9:33 ` [PATCH v2 2/3] dmaengine: Remove dma_request_slave_channel_compat() wrapper Geert Uytterhoeven
2020-01-21 9:33 ` [PATCH v2 3/3] dmaengine: Move dma_get_{,any_}slave_channel() to private dmaengine.h Geert Uytterhoeven
2020-01-21 9:35 ` [PATCH v2 0/3] dmaengine: Miscellaneous cleanups Vinod Koul
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=20200121093311.28639-1-geert+renesas@glider.be \
--to=geert+renesas@glider.be \
--cc=arnd@arndb.de \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=lars@metafoo.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mporter@konsulko.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).