From: Fan Fei <ffclaire1224@gmail.com>
To: bjorn@helgaas.com
Cc: Fan Fei <ffclaire1224@gmail.com>, linux-pci@vger.kernel.org
Subject: [PATCH 00/13] Unify device * to platform_device *
Date: Sat, 27 Nov 2021 15:11:08 +0100 [thread overview]
Message-ID: <cover.1638022048.git.ffclaire1224@gmail.com> (raw)
Some PCI controller structs contain "device *", while others contain
"platform_device *". These patches unify "device *dev" to
"platform_device *pdev" in 13 controller struct, to make the controller
struct more consistent. Consider that PCI controllers interact with
platform_device directly, not device, to enumerate the controlled device.
Fan Fei (13):
PCI: xilinx: Replace device * with platform_device *
PCI: mediatek: Replace device * with platform_device *
PCI: tegra: Replace device * with platform_device *
PCI: xegene: Replace device * with platform_device *
PCI: microchip: Replace device * with platform_device *
PCI: brcmstb: Replace device * with platform_device *
PCI: mediatek-gen3: Replace device * with platform_device *
PCI: rcar-gen2: Replace device * with platform_device *
PCI: ftpci100: Replace device * with platform_device *
PCI: v3-semi: Replace device * with platform_device *
PCI: ixp4xx: Replace device * with platform_device *
PCI: xilinx-nwl: Replace device * with platform_device *
PCI: rcar: Replace device * with platform_device *
drivers/pci/controller/pci-ftpci100.c | 15 +-
drivers/pci/controller/pci-ixp4xx.c | 47 ++--
drivers/pci/controller/pci-rcar-gen2.c | 10 +-
drivers/pci/controller/pci-tegra.c | 85 +++----
drivers/pci/controller/pci-v3-semi.c | 19 +-
drivers/pci/controller/pci-xgene.c | 222 +++++++++----------
drivers/pci/controller/pcie-brcmstb.c | 35 +--
drivers/pci/controller/pcie-mediatek-gen3.c | 36 +--
drivers/pci/controller/pcie-mediatek.c | 31 +--
drivers/pci/controller/pcie-microchip-host.c | 18 +-
drivers/pci/controller/pcie-rcar-ep.c | 40 ++--
drivers/pci/controller/pcie-rcar-host.c | 27 +--
drivers/pci/controller/pcie-rcar.h | 2 +-
drivers/pci/controller/pcie-xilinx-nwl.c | 28 +--
drivers/pci/controller/pcie-xilinx.c | 21 +-
15 files changed, 328 insertions(+), 308 deletions(-)
--
2.25.1
next reply other threads:[~2021-11-27 14:16 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-27 14:11 Fan Fei [this message]
2021-11-27 14:11 ` [PATCH 01/13] PCI: xilinx: Replace device * with platform_device * Fan Fei
2021-11-27 14:11 ` [PATCH 02/13] PCI: mediatek: " Fan Fei
2021-11-27 14:11 ` [PATCH 03/13] PCI: tegra: " Fan Fei
2021-11-27 14:11 ` [PATCH 04/13] PCI: xegene: " Fan Fei
2021-11-27 14:11 ` [PATCH 05/13] PCI: microchip: " Fan Fei
2021-11-27 14:11 ` [PATCH 06/13] PCI: brcmstb: " Fan Fei
2021-11-27 14:11 ` [PATCH 07/13] PCI: mediatek-gen3: " Fan Fei
2021-11-27 14:11 ` [PATCH 08/13] PCI: rcar-gen2: " Fan Fei
2021-11-27 14:11 ` [PATCH 09/13] PCI: ftpci100: " Fan Fei
2021-11-27 14:11 ` [PATCH 10/13] PCI: v3-semi: " Fan Fei
2021-11-27 14:11 ` [PATCH 11/13] PCI: ixp4xx: " Fan Fei
2021-11-27 14:11 ` [PATCH 12/13] PCI: xilinx-nwl: " Fan Fei
2021-11-27 14:11 ` [PATCH 13/13] PCI: rcar: " Fan Fei
2021-12-23 0:43 ` [PATCH 00/13] Unify device * to " Bjorn Helgaas
2021-12-28 19:38 ` Fan Fei
2021-12-29 17:14 ` Bjorn Helgaas
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=cover.1638022048.git.ffclaire1224@gmail.com \
--to=ffclaire1224@gmail.com \
--cc=bjorn@helgaas.com \
--cc=linux-pci@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).