From: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
Ralf Baechle <ralf@linux-mips.org>,
Manuel Lauss <manuel.lauss@gmail.com>
Cc: James Hogan <james.hogan@imgtec.com>,
Bjorn Helgaas <bhelgaas@google.com>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: linux-next: manual merge of the mips tree with the pci-current tree
Date: Fri, 22 Sep 2017 10:20:09 +0100 [thread overview]
Message-ID: <20170922092009.GA1523@red-moon> (raw)
In-Reply-To: <20170922100114.569b940e@canb.auug.org.au>
Manuel, Ralf,
On Fri, Sep 22, 2017 at 10:01:14AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the mips tree got a conflict in:
>
> arch/mips/pci/pci-octeon.c
>
> between commit:
>
> 19a8d6b7604d ("MIPS: PCI: Move map_irq() hooks out of initdata")
This commit (coming from the PCI tree) should be a superset of the fix
in the MIPS tree below, do you mind having a look please and if that's
the case drop commit below from the MIPS tree please ?
> from the pci-current tree and commit:
>
> 8eba3651f1da ("MIPS: PCI: fix pcibios_map_irq section mismatch")
>
> from the mips tree.
>
> I fixed it up (basically the same patch - I used the pci-current tree
> version) 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.
I had no idea of:
8eba3651f1da ("MIPS: PCI: fix pcibios_map_irq section mismatch")
existence, apologies.
Lorenzo
prev parent reply other threads:[~2017-09-22 9:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-22 0:01 linux-next: manual merge of the mips tree with the pci-current tree Stephen Rothwell
2017-09-22 9:20 ` Lorenzo Pieralisi [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=20170922092009.GA1523@red-moon \
--to=lorenzo.pieralisi@arm.com \
--cc=bhelgaas@google.com \
--cc=james.hogan@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=manuel.lauss@gmail.com \
--cc=ralf@linux-mips.org \
--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 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).