From: Vinod Koul <vkoul@kernel.org>
To: dmaengine@vger.kernel.org
Cc: Vinod Koul <vkoul@kernel.org>
Subject: [PATCH 0/4] dmaengine: use inclusive terminology
Date: Thu, 15 Oct 2020 13:01:28 +0530 [thread overview]
Message-ID: <20201015073132.3571684-1-vkoul@kernel.org> (raw)
dmaengine history has a non inclusive terminology of dmaengine slave, I
feel it is time to replace that. This series starts the work by replacing
slave with peripheral as I feel this is an appropriate term for dmaengine
peripheral devices.
This series updates the header for dmaengine and use macros to keep existing
name to avoid breaking users. If people are okay with this, I will post rest
of the pile which does conversion for whole subsystem. After next cycle we
will move users and once that is done drop the macros.
Vinod Koul (4):
dmaengine: move enums in interface to use peripheral term
dmaengine: move struct in interface to use peripheral term
dmaengine: move APIs in interface to use peripheral term
dmaengine: core: update to use peripheral term
drivers/dma/dmaengine.c | 48 ++++++------
include/linux/dmaengine.h | 161 +++++++++++++++++++++++---------------
2 files changed, 124 insertions(+), 85 deletions(-)
--
2.26.2
next reply other threads:[~2020-10-15 7:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-15 7:31 Vinod Koul [this message]
2020-10-15 7:31 ` [PATCH 1/4] dmaengine: move enums in interface to use peripheral term Vinod Koul
2020-10-19 8:54 ` Peter Ujfalusi
2020-10-27 17:11 ` Vinod Koul
2020-10-15 7:31 ` [PATCH 2/4] dmaengine: move struct " Vinod Koul
2020-10-19 9:04 ` Peter Ujfalusi
2020-10-27 17:16 ` Vinod Koul
2020-10-15 7:31 ` [PATCH 3/4] dmaengine: move APIs " Vinod Koul
2020-10-19 9:17 ` Peter Ujfalusi
2020-10-28 4:33 ` Vinod Koul
2020-10-15 7:31 ` [PATCH 4/4] dmaengine: core: update " 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=20201015073132.3571684-1-vkoul@kernel.org \
--to=vkoul@kernel.org \
--cc=dmaengine@vger.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).