From: Lorenzo Pieralisi <lpieralisi@kernel.org>
To: Michal Simek <michal.simek@amd.com>
Cc: Thippeswamy Havalige <thippeswamy.havalige@amd.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org, krzysztof.kozlowski@linaro.org,
bhelgaas@google.com, michals@xilinx.com, robh+dt@kernel.org,
lorenzo.pieralisi@arm.com, bharat.kumar.gogada@amd.com
Subject: Re: [PATCH 00/13] Remove unused microblaze PCIe bus architecture
Date: Thu, 27 Oct 2022 11:46:47 +0200 [thread overview]
Message-ID: <Y1pTh5fiN+/mKPrR@lpieralisi> (raw)
In-Reply-To: <06718d29-f3e1-db07-d537-b78290213b10@amd.com>
On Tue, Oct 25, 2022 at 09:31:37AM +0200, Michal Simek wrote:
> Hi,
>
> On 10/25/22 08:52, Thippeswamy Havalige wrote:
> > The current Xilinx AXI PCIe Host Bridge driver uses generic PCIe
> > subsystem framework. This driver works on both Microblaze and Zynq
> > architecture based platforms.
> >
> > The microblaze architecture specific code has unused PCIe host bridge
> > supported API's which are no longer needed.
> >
> > This series of patch removes unused architecture specific
> > microblaze PCIe code.
> >
> > Thippeswamy Havalige (13):
> > microblaze/PCI: Remove unused early_read_config_byte() et al
> > declarations
> > microblaze/PCI: Remove Null PCI config access unused functions
> > microblaze/PCI: Remove unused PCI bus scan if configured as a host
> > microblaze/PCI: Remove unused PCI legacy IO's access on a bus
> > microblaze/PCI: Remove unused device tree parsing for a host bridge
> > resources
> > microblaze/PCI: Remove unused allocation & free of PCI host bridge
> > structure
> > microblaze/PCI: Remove unused PCI BIOS resource allocation
> > microblaze/PCI: Remove unused PCI Indirect ops
> > microblaze/PCI: Remove unused pci_address_to_pio() conversion of CPU
> > address to I/O port
> > microblaze/PCI: Remove unused sys_pciconfig_iobase() and et al
> > declaration
> > microblaze/PCI: Remove unused pci_iobar_pfn() and et al declarations
> > microblaze/PCI: Remove support for Xilinx PCI host bridge
> > microblaze/PCI: Moving PCI iounmap and dependent code
> >
> > arch/microblaze/Kconfig | 8 -
> > arch/microblaze/include/asm/pci-bridge.h | 92 ---
> > arch/microblaze/include/asm/pci.h | 29 -
> > arch/microblaze/pci/Makefile | 3 +-
> > arch/microblaze/pci/indirect_pci.c | 158 -----
> > arch/microblaze/pci/iomap.c | 36 +
> > arch/microblaze/pci/pci-common.c | 1067 ------------------------------
> > arch/microblaze/pci/xilinx_pci.c | 170 -----
> > 8 files changed, 37 insertions(+), 1526 deletions(-)
> > delete mode 100644 arch/microblaze/pci/indirect_pci.c
> > delete mode 100644 arch/microblaze/pci/pci-common.c
> > delete mode 100644 arch/microblaze/pci/xilinx_pci.c
> >
>
> Why are you sending it again?
Michal,
it looks like you don't need anything from me or Bjorn on this series so
I shall drop it from the PCI queue and let you handle it.
If you need any help please let me know.
Thanks,
Lorenzo
next prev parent reply other threads:[~2022-10-27 9:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-25 6:52 [PATCH 00/13] Remove unused microblaze PCIe bus architecture Thippeswamy Havalige
2022-10-25 6:52 ` [PATCH 01/13] microblaze/PCI: Remove unused early_read_config_byte() et al declarations Thippeswamy Havalige
2022-10-25 6:52 ` [PATCH 02/13] microblaze/PCI: Remove Null PCI config access unused functions Thippeswamy Havalige
2022-10-25 6:52 ` [PATCH 03/13] microblaze/PCI: Remove unused PCI bus scan if configured as a host Thippeswamy Havalige
2022-10-25 6:52 ` [PATCH 04/13] microblaze/PCI: Remove unused PCI legacy IO's access on a bus Thippeswamy Havalige
2022-10-25 6:52 ` [PATCH 05/13] microblaze/PCI: Remove unused device tree parsing for a host bridge resources Thippeswamy Havalige
2022-10-25 6:52 ` [PATCH 06/13] microblaze/PCI: Remove unused allocation & free of PCI host bridge structure Thippeswamy Havalige
2022-10-25 6:52 ` [PATCH 07/13] microblaze/PCI: Remove unused PCI BIOS resource allocation Thippeswamy Havalige
2022-10-25 6:52 ` [PATCH 08/13] microblaze/PCI: Remove unused PCI Indirect ops Thippeswamy Havalige
2022-10-25 6:52 ` [PATCH 09/13] microblaze/PCI: Remove unused pci_address_to_pio() conversion of CPU address to I/O port Thippeswamy Havalige
2022-10-25 6:52 ` [PATCH 10/13] microblaze/PCI: Remove unused sys_pciconfig_iobase() and et al declaration Thippeswamy Havalige
2022-10-25 6:52 ` [PATCH 11/13] microblaze/PCI: Remove unused pci_iobar_pfn() and et al declarations Thippeswamy Havalige
2022-10-25 6:52 ` [PATCH 12/13] microblaze/PCI: Remove support for Xilinx PCI host bridge Thippeswamy Havalige
2022-10-25 6:52 ` [PATCH 13/13] microblaze/PCI: Moving PCI iounmap and dependent code Thippeswamy Havalige
2022-10-25 7:31 ` [PATCH 00/13] Remove unused microblaze PCIe bus architecture Michal Simek
2022-10-25 8:26 ` Havalige, Thippeswamy
2022-10-25 9:22 ` Michal Simek
2022-10-25 14:07 ` Havalige, Thippeswamy
2022-10-27 9:46 ` Lorenzo Pieralisi [this message]
2022-11-04 8:56 ` Havalige, Thippeswamy
2022-11-25 10:39 ` Michal Simek
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=Y1pTh5fiN+/mKPrR@lpieralisi \
--to=lpieralisi@kernel.org \
--cc=bharat.kumar.gogada@amd.com \
--cc=bhelgaas@google.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=michal.simek@amd.com \
--cc=michals@xilinx.com \
--cc=robh+dt@kernel.org \
--cc=thippeswamy.havalige@amd.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).