From: Qing Wang <wangqing@vivo.com>
To: Gustavo Pimentel <gustavo.pimentel@synopsys.com>,
Vinod Koul <vkoul@kernel.org>, Viresh Kumar <vireshk@kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Zhou Wang <wangzhou1@hisilicon.com>,
Logan Gunthorpe <logang@deltatee.com>,
Sathya Prakash <sathya.prakash@broadcom.com>,
Sreekanth Reddy <sreekanth.reddy@broadcom.com>,
Suganath Prabu Subramani <suganath-prabu.subramani@broadcom.com>,
dmaengine@vger.kernel.org, linux-kernel@vger.kernel.org,
MPT-FusionLinux.pdl@broadcom.com, linux-scsi@vger.kernel.org
Cc: Qing Wang <wangqing@vivo.com>
Subject: [PATCH V3 0/7] switch from 'pci_' to 'dma_' API
Date: Thu, 7 Oct 2021 20:28:26 -0700 [thread overview]
Message-ID: <1633663733-47199-1-git-send-email-wangqing@vivo.com> (raw)
The wrappers in include/linux/pci-dma-compat.h should go away.
The patch has been generated with the coccinelle script below.
expression e1, e2;
@@
- pci_set_dma_mask(e1, e2)
+ dma_set_mask(&e1->dev, e2)
@@
expression e1, e2;
@@
- pci_set_consistent_dma_mask(e1, e2)
+ dma_set_coherent_mask(&e1->dev, e2)
While at it, some 'dma_set_mask()/dma_set_coherent_mask()' have been
updated to a much less verbose 'dma_set_mask_and_coherent()'.
This type of patches has been going on for a long time, I plan to
clean it up in the near future. If needed, see post from
Christoph Hellwig on the kernel-janitors ML:
https://marc.info/?l=kernel-janitors&m=158745678307186&w=4
Qing Wang (7):
dma: dw-edma-pcie: switch from 'pci_' to 'dma_' API
dma: dw: switch from 'pci_' to 'dma_' API
dma: hisi_dma: switch from 'pci_' to 'dma_' API
dma: hsu: switch from 'pci_' to 'dma_' API
dma: ioat: switch from 'pci_' to 'dma_' API
dma: dmaengine: switch from 'pci_' to 'dma_' API
message: fusion: switch from 'pci_' to 'dma_' API
drivers/dma/dw-edma/dw-edma-pcie.c | 17 ++++-------------
drivers/dma/dw/pci.c | 6 +-----
drivers/dma/hisi_dma.c | 6 +-----
drivers/dma/hsu/pci.c | 6 +-----
drivers/dma/ioat/init.c | 10 ++--------
drivers/dma/plx_dma.c | 10 ++--------
drivers/message/fusion/mptbase.c | 31 +++++++++----------------------
7 files changed, 20 insertions(+), 66 deletions(-)
--
2.7.4
next reply other threads:[~2021-10-08 3:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-08 3:28 Qing Wang [this message]
2021-10-08 3:28 ` [PATCH V3 1/7] dma: dw-edma-pcie: switch from 'pci_' to 'dma_' API Qing Wang
2021-10-08 3:28 ` [PATCH V3 5/7] dma: ioat: " Qing Wang
2021-10-08 3:28 ` [PATCH V3 4/7] dma: hsu: " Qing Wang
2021-10-08 3:28 ` [PATCH V3 3/7] dma: hisi_dma: " Qing Wang
2021-10-08 3:28 ` [PATCH V3 2/7] dma: dw: " Qing Wang
2021-10-08 3:28 ` [PATCH V3 6/7] dma: dmaengine: " Qing Wang
2021-10-08 3:28 ` [PATCH V3 7/7] message: fusion: " Qing Wang
2021-10-25 6:55 ` [PATCH V3 0/7] " 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=1633663733-47199-1-git-send-email-wangqing@vivo.com \
--to=wangqing@vivo.com \
--cc=MPT-FusionLinux.pdl@broadcom.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=gustavo.pimentel@synopsys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=logang@deltatee.com \
--cc=sathya.prakash@broadcom.com \
--cc=sreekanth.reddy@broadcom.com \
--cc=suganath-prabu.subramani@broadcom.com \
--cc=vireshk@kernel.org \
--cc=vkoul@kernel.org \
--cc=wangzhou1@hisilicon.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).