From: Stafford Horne <shorne@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>, Stafford Horne <shorne@gmail.com>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>, Guo Ren <guoren@kernel.org>,
linux-riscv@lists.infradead.org, linux-csky@vger.kernel.org
Subject: [PATCH v3 0/2] Updates for asm-generic/pci.h
Date: Mon, 18 Jul 2022 09:41:12 +0900 [thread overview]
Message-ID: <20220718004114.3925745-1-shorne@gmail.com> (raw)
When reviewing the OpenRISC PCI support patch Arnd suggested that
we avoid copying arm64 and riscv asm/pci.h and moving that to be
the new asm-generic/pci.h.
This patch does that by first moving the old pci.h definition
of pci_get_legacy_ide_irq out to the architectures that use it,
this turns out to only be x86.
Next, we create the new pci.h definition.
Note, for the series, I am working on these fixups as part of adding PCI to
OpenRISC. If the series is accepted I would like to merge via the OpenRISC tree
with the OpenRISC PCI support patches to avoid having to coordinate upstream
merges.
Since v2:
- Remove pci_get_legacy_ide_irq from m68k.
Since v1:
- Remove definition of pci_get_legacy_ide_irq on architectures
not using CONFIG_PNP, which eliminated most.
- Add ifdef around PCIBIOS_MIN_MEM for consistency.
Stafford Horne (2):
asm-generic: Remove pci.h copying remaining code to x86
asm-generic: Add new pci.h and use it
arch/alpha/include/asm/pci.h | 1 -
arch/arm64/include/asm/pci.h | 12 +++------
arch/csky/include/asm/pci.h | 24 +++--------------
arch/ia64/include/asm/pci.h | 1 -
arch/m68k/include/asm/pci.h | 2 --
arch/powerpc/include/asm/pci.h | 1 -
arch/riscv/include/asm/pci.h | 25 +++---------------
arch/s390/include/asm/pci.h | 1 -
arch/sparc/include/asm/pci.h | 9 -------
arch/um/include/asm/pci.h | 24 ++---------------
arch/x86/include/asm/pci.h | 6 +++--
arch/xtensa/include/asm/pci.h | 3 ---
include/asm-generic/pci.h | 47 ++++++++++++++++++++++++----------
13 files changed, 49 insertions(+), 107 deletions(-)
--
2.36.1
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2022-07-18 0:41 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 0:41 Stafford Horne [this message]
2022-07-18 0:41 ` [PATCH v3 1/2] asm-generic: Remove pci.h copying remaining code to x86 Stafford Horne
2022-07-18 8:22 ` Geert Uytterhoeven
2022-07-19 12:02 ` Pierre Morel
2022-07-18 0:41 ` [PATCH v3 2/2] asm-generic: Add new pci.h and use it Stafford Horne
2022-07-19 15:58 ` Palmer Dabbelt
2022-07-21 22:05 ` Stafford Horne
2022-07-21 22:53 ` Palmer Dabbelt
2022-07-21 23:06 ` Rob Herring
2022-07-22 10:53 ` Arnd Bergmann
2022-07-22 15:27 ` Palmer Dabbelt
2022-07-22 16:36 ` Rob Herring
2022-07-22 19:23 ` Maciej W. Rozycki
2022-07-22 19:42 ` Rob Herring
2022-07-22 22:28 ` Maciej W. Rozycki
2022-07-22 19:55 ` Arnd Bergmann
2022-07-22 21:39 ` Jessica Clarke
2022-07-22 21:44 ` Rob Herring
2022-07-22 22:41 ` Maciej W. Rozycki
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=20220718004114.3925745-1-shorne@gmail.com \
--to=shorne@gmail.com \
--cc=aou@eecs.berkeley.edu \
--cc=arnd@arndb.de \
--cc=guoren@kernel.org \
--cc=linux-csky@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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