From: Stafford Horne <shorne@gmail.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Bjorn Helgaas <bhelgaas@google.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Paul Walmsley <paul@pwsan.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux Next Mailing List <linux-next@vger.kernel.org>,
"Maciej W. Rozycki" <macro@orcam.me.uk>,
Palmer Dabbelt <palmer@rivosinc.com>
Subject: Re: linux-next: manual merge of the pci tree with the risc-v tree
Date: Mon, 25 Jul 2022 09:59:04 +0900 [thread overview]
Message-ID: <Yt3q2LX4ds9lwXW+@antec> (raw)
In-Reply-To: <20220725102221.20fe2ca2@canb.auug.org.au>
On Mon, Jul 25, 2022 at 10:22:21AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the pci tree got a conflict in:
>
> arch/riscv/include/asm/pci.h
>
> between commit:
>
> bb356ddb78b2 ("RISC-V: PCI: Avoid handing out address 0 to devices")
>
> from the risc-v tree and commit:
>
> a2912b45b082 ("asm-generic: Add new pci.h and use it")
>
> from the pci tree.
Hi Stephen,
We had anticipated this and I believe Palmer should be merging the pci changes
to his branch to resolve the merge conflict before sending the changes upstream.
> I fixed it up (see below) and can carry the fix as necessary. This
> is now fixed as far as linux-next is concerned, but any non trivial
> conflicts should be mentioned to your upstream maintainer when your tree
> is submitted for merging. You may also want to consider cooperating
> with the maintainer of the conflicting tree to minimise any particularly
> complex conflicts.
>
> --
> Cheers,
> Stephen Rothwell
>
> diff --cc arch/riscv/include/asm/pci.h
> index 830ac621dbbc,6ef4a1426194..000000000000
> --- a/arch/riscv/include/asm/pci.h
> +++ b/arch/riscv/include/asm/pci.h
> @@@ -12,31 -12,7 +12,10 @@@
>
> #include <asm/io.h>
>
> +#define PCIBIOS_MIN_IO 4
> +#define PCIBIOS_MIN_MEM 16
> +
> - /* RISC-V shim does not initialize PCI bus */
> - #define pcibios_assign_all_busses() 1
> -
> - #define ARCH_GENERIC_PCI_MMAP_RESOURCE 1
> -
> - extern int isa_dma_bridge_buggy;
> -
> - #ifdef CONFIG_PCI
> - static inline int pci_get_legacy_ide_irq(struct pci_dev *dev, int channel)
> - {
> - /* no legacy IRQ on risc-v */
> - return -ENODEV;
> - }
> -
> - static inline int pci_proc_domain(struct pci_bus *bus)
> - {
> - /* always show the domain in /proc */
> - return 1;
> - }
> -
> - #ifdef CONFIG_NUMA
> -
> + #if defined(CONFIG_PCI) && defined(CONFIG_NUMA)
> static inline int pcibus_to_node(struct pci_bus *bus)
> {
> return dev_to_node(&bus->dev);
Your conflict resolution patch looks good to me.
-Stafford
prev parent reply other threads:[~2022-07-25 0:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-25 0:22 linux-next: manual merge of the pci tree with the risc-v tree Stephen Rothwell
2022-07-25 0:59 ` Stafford Horne [this message]
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=Yt3q2LX4ds9lwXW+@antec \
--to=shorne@gmail.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=macro@orcam.me.uk \
--cc=palmer@dabbelt.com \
--cc=palmer@rivosinc.com \
--cc=paul@pwsan.com \
--cc=sfr@canb.auug.org.au \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.