From: Michal Simek <monstr@monstr.eu>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: [GIT PULL] arch/microblaze patches for 6.2-rc1
Date: Thu, 8 Dec 2022 11:07:27 +0100 [thread overview]
Message-ID: <b7ece19c-e50e-0709-7be1-2945883d155b@monstr.eu> (raw)
Hi Linus,
please pull these changes to your tree. They are cleaning up the PCI bus support
which was pretty much c&p from PowerPC long time ago for one custom platform
which is not available for years. Finally Xilinx/AMD PCIe team tested Microblaze
with IP cores also used on ARM SOCs and clean up Microblaze code.
Thanks,
Michal
The following changes since commit 9abf2313adc1ca1b6180c508c25f22f9395cc780:
Linux 6.1-rc1 (2022-10-16 15:36:24 -0700)
are available in the Git repository at:
git://git.monstr.eu/linux-2.6-microblaze.git tags/microblaze-v6.2
for you to fetch changes up to 5cfe469c2654c3a4dda8504b1209abdd8b379e95:
microblaze/PCI: Moving PCI iounmap and dependent code (2022-11-25 11:39:23 +0100)
----------------------------------------------------------------
Microblaze patches for 6.2-rc1
- Cleanup PCI support
----------------------------------------------------------------
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/configs/mmu_defconfig | 1 -
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 ----
9 files changed, 37 insertions(+), 1527 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
--
Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91
w: www.monstr.eu p: +42-0-721842854
Maintainer of Linux kernel - Xilinx Microblaze
Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs
U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP/Versal SoCs
next reply other threads:[~2022-12-08 10:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 10:07 Michal Simek [this message]
2022-12-12 17:49 ` Linus Torvalds
2022-12-13 7:53 ` Michal Simek
2022-12-12 18:07 ` pr-tracker-bot
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=b7ece19c-e50e-0709-7be1-2945883d155b@monstr.eu \
--to=monstr@monstr.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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
all inboxes | Powered by JetHome®