From: Simon Horman <horms@verge.net.au>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
ARM <linux-arm-kernel@lists.infradead.org>,
Heiko Stuebner <heiko@sntech.de>,
Linux-Next Mailing List <linux-next@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Ezequiel Garcia <ezequiel@collabora.com>
Subject: Re: linux-next: manual merge of the rockchip tree with the renesas tree
Date: Wed, 16 May 2018 08:44:45 +0200 [thread overview]
Message-ID: <20180516064440.xpwm7liozhvx4aro@verge.net.au> (raw)
In-Reply-To: <20180516113918.1ccdd8ec@canb.auug.org.au>
Thanks Stephen,
On Wed, May 16, 2018 at 11:39:18AM +1000, Stephen Rothwell wrote:
> Hi all,
>
> On Thu, 3 May 2018 08:36:54 +1000 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> >
> > Today's linux-next merge of the rockchip tree got a conflict in:
> >
> > arch/arm64/configs/defconfig
> >
> > between commits:
> >
> > 93f7bfd930c0 ("arm64: defconfig: makes SND_SIMPLE_CARD to module")
> > ddf3fa8b8a16 ("arm64: defconfig: Enable CONFIG_SND_AUDIO_GRAPH_CARD")
> >
> > from the renesas tree and commit:
> >
> > e9cfce4195ec ("arm64: defconfig: Enable HID over I2C drivers")
> >
> > from the rockchip tree.
> >
> > 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.
The resolution looks correct to me.
As the renesas tree reaches Linus via the arm-soc tree I believe
this is likely best resolved by the arm-soc maintainers once I
send them a pull-request for the renesas tree. And I do not expect
it to bubble-up to Linus.
> >
> > --
> > Cheers,
> > Stephen Rothwell
> >
> > diff --cc arch/arm64/configs/defconfig
> > index 7930caf5dde4,34037d24fbf4..000000000000
> > --- a/arch/arm64/configs/defconfig
> > +++ b/arch/arm64/configs/defconfig
> > @@@ -158,9 -157,9 +158,10 @@@ CONFIG_BT_HIDP=
> > # CONFIG_BT_LE is not set
> > CONFIG_BT_LEDS=y
> > # CONFIG_BT_DEBUGFS is not set
> > + CONFIG_BT_HCIBTUSB=m
> > CONFIG_BT_HCIUART=m
> > CONFIG_BT_HCIUART_LL=y
> > +CONFIG_BT_HCIUART_BCM=y
> > CONFIG_CFG80211=m
> > CONFIG_MAC80211=m
> > CONFIG_MAC80211_LEDS=y
> > @@@ -443,8 -447,8 +451,9 @@@ CONFIG_SND_BCM2835_SOC_I2S=
> > CONFIG_SND_SOC_SAMSUNG=y
> > CONFIG_SND_SOC_RCAR=m
> > CONFIG_SND_SOC_AK4613=m
> > -CONFIG_SND_SIMPLE_CARD=y
> > +CONFIG_SND_SIMPLE_CARD=m
> > +CONFIG_SND_AUDIO_GRAPH_CARD=m
> > + CONFIG_I2C_HID=m
> > CONFIG_USB=y
> > CONFIG_USB_OTG=y
> > CONFIG_USB_XHCI_HCD=y
>
> This is now a conflict between the renesas tree and the arm-soc tree.
>
> --
> Cheers,
> Stephen Rothwell
prev parent reply other threads:[~2018-05-16 6:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 22:36 linux-next: manual merge of the rockchip tree with the renesas tree Stephen Rothwell
2018-05-03 6:43 ` Simon Horman
2018-05-16 1:39 ` Stephen Rothwell
2018-05-16 6:44 ` Simon Horman [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=20180516064440.xpwm7liozhvx4aro@verge.net.au \
--to=horms@verge.net.au \
--cc=arnd@arndb.de \
--cc=ezequiel@collabora.com \
--cc=heiko@sntech.de \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=olof@lixom.net \
--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