All of lore.kernel.org
 help / color / mirror / Atom feed
From: Conor Dooley <conor.dooley@microchip.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: Re: linux-next: manual merge of the risc-v-mc tree with Linus' tree
Date: Tue, 20 Sep 2022 07:29:13 +0100	[thread overview]
Message-ID: <YylduXa12mtakuHT@wendy> (raw)
In-Reply-To: <20220920051905.500a52ce@canb.auug.org.au>

On Tue, Sep 20, 2022 at 05:19:05AM +1000, Stephen Rothwell wrote:
> Hi all,
> 
> Today's linux-next merge of the risc-v-mc tree got a conflict in:
> 
>   arch/riscv/boot/dts/microchip/mpfs.dtsi
> 
> between commits:
> 
>   3f67e6997603 ("riscv: dts: microchip: mpfs: fix incorrect pcie child node name")
>   e4009c5fa77b ("riscv: dts: microchip: mpfs: remove pci axi address translation property")
> 
> from Linus' tree and commit:
> 
>   2ad0883d86c8 ("riscv: dts: microchip: move the mpfs' pci node to -fabric.dtsi")
> 
> from the risc-v-mc tree.
> 
> I fixed it up (the latter change seems to include the other 2) and can

Yup, I test merged it after applying and that was my resolution too.
Thanks Stephen.

> 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



      reply	other threads:[~2022-09-20  6:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-19 19:19 linux-next: manual merge of the risc-v-mc tree with Linus' tree Stephen Rothwell
2022-09-20  6:29 ` Conor Dooley [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=YylduXa12mtakuHT@wendy \
    --to=conor.dooley@microchip.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.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 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.