From: Stephen Warren <swarren@wwwdotorg.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>,
linux-arm-kernel@lists.infradead.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org, Stephen Warren <swarren@nvidia.com>
Subject: Re: linux-next: manual merge of the arm-soc tree with Linus' tree
Date: Tue, 27 Aug 2013 10:17:21 -0600 [thread overview]
Message-ID: <521CD111.9030905@wwwdotorg.org> (raw)
In-Reply-To: <20130827182935.ff4005b60cc1ce80d32d5e46@canb.auug.org.au>
On 08/27/2013 02:29 AM, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the arm-soc tree got a conflict in
> arch/arm/boot/dts/tegra20-trimslice.dts between commit
> 30ca2226bea6 ("ARM: tegra: always enable USB VBUS regulators") from
> Linus' tree and commit 23f95ef2d951 ("ARM: tegra: use TEGRA_GPIO()
> in a couple more places") from the arm-soc tree.
>
> I fixed it up (see below) and can carry the fix as necessary (no
> action is required).
> diff --cc arch/arm/boot/dts/tegra20-trimslice.dts
> usb@c5000000 { status = "okay"; - nvidia,vbus-gpio = <&gpio
> TEGRA_GPIO(V, 2) GPIO_ACTIVE_HIGH>; };
That chunk isn't part of either of the two commits above.
It is however part of commit 103566e "arm: tegra: Remove obsolete
nvidia,vbus-gpio properties" from the USB tree, so it's fine that the
change is part of linux-next.
I'm just not sure if it's expected for that chunk to show up in this
merge resolution email? If it's normal, then there's no problem; the
issue would be with me not having too much git merge conflict
resolution experience:-)
WARNING: multiple messages have this Message-ID (diff)
From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next: manual merge of the arm-soc tree with Linus' tree
Date: Tue, 27 Aug 2013 10:17:21 -0600 [thread overview]
Message-ID: <521CD111.9030905@wwwdotorg.org> (raw)
In-Reply-To: <20130827182935.ff4005b60cc1ce80d32d5e46@canb.auug.org.au>
On 08/27/2013 02:29 AM, Stephen Rothwell wrote:
> Hi all,
>
> Today's linux-next merge of the arm-soc tree got a conflict in
> arch/arm/boot/dts/tegra20-trimslice.dts between commit
> 30ca2226bea6 ("ARM: tegra: always enable USB VBUS regulators") from
> Linus' tree and commit 23f95ef2d951 ("ARM: tegra: use TEGRA_GPIO()
> in a couple more places") from the arm-soc tree.
>
> I fixed it up (see below) and can carry the fix as necessary (no
> action is required).
> diff --cc arch/arm/boot/dts/tegra20-trimslice.dts
> usb at c5000000 { status = "okay"; - nvidia,vbus-gpio = <&gpio
> TEGRA_GPIO(V, 2) GPIO_ACTIVE_HIGH>; };
That chunk isn't part of either of the two commits above.
It is however part of commit 103566e "arm: tegra: Remove obsolete
nvidia,vbus-gpio properties" from the USB tree, so it's fine that the
change is part of linux-next.
I'm just not sure if it's expected for that chunk to show up in this
merge resolution email? If it's normal, then there's no problem; the
issue would be with me not having too much git merge conflict
resolution experience:-)
next prev parent reply other threads:[~2013-08-27 16:17 UTC|newest]
Thread overview: 84+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-27 8:29 linux-next: manual merge of the arm-soc tree with Linus' tree Stephen Rothwell
2013-08-27 8:29 ` Stephen Rothwell
2013-08-27 8:29 ` Stephen Rothwell
2013-08-27 16:17 ` Stephen Warren [this message]
2013-08-27 16:17 ` Stephen Warren
2013-08-28 0:06 ` Stephen Rothwell
2013-08-28 0:06 ` Stephen Rothwell
-- strict thread matches above, loose matches on Subject: below --
2022-05-27 0:39 Stephen Rothwell
2022-05-27 0:39 ` Stephen Rothwell
2022-05-27 15:38 ` Hawkins, Nick
2022-05-27 15:38 ` Hawkins, Nick
2022-05-28 0:29 ` Stephen Rothwell
2022-05-28 0:29 ` Stephen Rothwell
2019-06-23 22:54 Stephen Rothwell
2019-06-23 22:54 ` Stephen Rothwell
2018-10-28 23:14 Stephen Rothwell
2018-10-28 23:14 ` Stephen Rothwell
2018-10-29 15:02 ` Tony Lindgren
2018-10-29 15:02 ` Tony Lindgren
2018-10-28 23:08 Stephen Rothwell
2018-10-28 23:08 ` Stephen Rothwell
2016-09-05 0:58 Stephen Rothwell
2016-09-05 0:58 ` Stephen Rothwell
2016-09-05 18:26 ` Russell King - ARM Linux
2016-09-05 18:26 ` Russell King - ARM Linux
2016-09-06 10:17 ` Arnd Bergmann
2016-09-06 10:17 ` Arnd Bergmann
2016-09-06 10:42 ` Russell King - ARM Linux
2016-09-06 10:42 ` Russell King - ARM Linux
2016-09-25 16:07 ` Robert Jarzmik
2016-09-25 16:07 ` Robert Jarzmik
2016-01-20 22:40 Stephen Rothwell
2016-01-20 22:40 ` Stephen Rothwell
2016-01-20 22:40 ` Stephen Rothwell
2015-08-23 23:55 Stephen Rothwell
2015-08-23 23:55 ` Stephen Rothwell
2015-08-23 23:55 ` Stephen Rothwell
2015-06-01 0:25 Stephen Rothwell
2015-06-01 0:25 ` Stephen Rothwell
2015-06-01 0:25 ` Stephen Rothwell
2015-06-01 7:12 ` Michal Simek
2015-06-01 7:12 ` Michal Simek
2014-01-30 0:19 Stephen Rothwell
2014-01-30 0:19 ` Stephen Rothwell
2014-01-30 0:19 ` Stephen Rothwell
2014-01-30 5:33 ` Kevin Hilman
2014-01-30 5:33 ` Kevin Hilman
2014-01-30 21:47 ` Mike Turquette
2014-01-30 21:47 ` Mike Turquette
2014-01-23 0:23 Stephen Rothwell
2014-01-23 0:23 ` Stephen Rothwell
2014-01-23 0:23 ` Stephen Rothwell
2013-08-27 8:26 Stephen Rothwell
2013-08-27 8:26 ` Stephen Rothwell
2013-08-27 8:26 ` Stephen Rothwell
2013-07-08 4:03 Stephen Rothwell
2013-07-08 4:03 ` Stephen Rothwell
2013-07-08 4:03 ` Stephen Rothwell
2013-03-18 3:49 Stephen Rothwell
2013-03-18 3:49 ` Stephen Rothwell
2013-03-18 3:49 ` Stephen Rothwell
2012-10-04 4:33 Stephen Rothwell
2012-10-04 4:33 ` Stephen Rothwell
2012-10-04 4:33 ` Stephen Rothwell
2012-07-30 2:53 Stephen Rothwell
2012-07-30 2:53 ` Stephen Rothwell
2012-07-30 2:53 ` Stephen Rothwell
2012-03-15 6:50 Stephen Rothwell
2012-03-15 6:50 ` Stephen Rothwell
2012-03-15 6:50 ` Stephen Rothwell
2012-03-15 9:51 ` Laurent Pinchart
2012-03-15 9:51 ` Laurent Pinchart
2012-03-15 20:01 ` Arnd Bergmann
2012-03-15 20:01 ` Arnd Bergmann
2012-03-15 21:36 ` Rafael J. Wysocki
2012-03-15 21:36 ` Rafael J. Wysocki
2012-03-08 6:07 Stephen Rothwell
2012-03-08 6:07 ` Stephen Rothwell
2012-03-08 6:07 ` Stephen Rothwell
2011-11-24 0:58 Stephen Rothwell
2011-11-24 0:58 ` Stephen Rothwell
2011-11-24 15:55 ` Arnd Bergmann
2011-11-06 23:33 Stephen Rothwell
2011-11-07 19:07 ` Arnd Bergmann
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=521CD111.9030905@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=arnd@arndb.de \
--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 \
--cc=swarren@nvidia.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 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.