From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arnd Bergmann Subject: Re: [GIT PULL 7/8] ARM: tegra: Devicetree changes for v4.2-rc1 Date: Fri, 15 May 2015 13:06:51 +0200 Message-ID: <5336613.jVykP4epFt@wuerfel> References: <1431524980-13599-1-git-send-email-thierry.reding@gmail.com> <3095273.etWfHSyyvC@wuerfel> <20150515104332.GB20474@ulmo.nvidia.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Return-path: In-Reply-To: <20150515104332.GB20474-AwZRO8vwLAwmlAP/+Wk3EA@public.gmane.org> Sender: linux-tegra-owner-u79uwXL29TY76Z2rM5mHXA@public.gmane.org To: Thierry Reding Cc: arm-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org, Stephen Warren , Alexandre Courbot , linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org, linux-arm-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org List-Id: linux-tegra@vger.kernel.org On Friday 15 May 2015 12:43:34 Thierry Reding wrote: > On Wed, May 13, 2015 at 06:09:20PM +0200, Arnd Bergmann wrote: > > On Wednesday 13 May 2015 15:49:39 Thierry Reding wrote: > > > ARM: tegra: Devicetree changes for v4.2-rc1 > > > > > > Contains a couple of fixes and additions to device tree files. The most > > > notable change is a fix for a misapplied patch that was only exposed by > > > a recent change in the regulator subsystem that caused USB to break on > > > Tegra124 recently. > > > > It sounds like I should merge commit a4b6916cb35 ("ARM: tegra: Correct > > which USB controller has the UTMI pad registers") into the 4.1 fixes > > branch as well. Please confirm. > > I think you already did. I sent out a pull request for that not very > long ago and I must have forgotten to drop this patch from the Tegra > tree after it got applied to arm-soc. The merge commit for this in > the fixes branch is here: > > https://git.kernel.org/cgit/linux/kernel/git/arm/arm-soc.git/commit/?h=fixes&id=155171274d1dd9d9e5a012bd912c592402aa31d2 > > Hopefully git will be able to merge these together without conflicts. > Sorry about the dupe. > Everything is fine. Since both branches have the same commit ID, git can figure out how to do the merges. It would only be annoying to get the same patch with two different commit IDs. Ideally, your pull request would mention this kind of situation, so I don't need to ask or research myself about it. Arnd From mboxrd@z Thu Jan 1 00:00:00 1970 From: arnd@arndb.de (Arnd Bergmann) Date: Fri, 15 May 2015 13:06:51 +0200 Subject: [GIT PULL 7/8] ARM: tegra: Devicetree changes for v4.2-rc1 In-Reply-To: <20150515104332.GB20474@ulmo.nvidia.com> References: <1431524980-13599-1-git-send-email-thierry.reding@gmail.com> <3095273.etWfHSyyvC@wuerfel> <20150515104332.GB20474@ulmo.nvidia.com> Message-ID: <5336613.jVykP4epFt@wuerfel> To: linux-arm-kernel@lists.infradead.org List-Id: linux-arm-kernel.lists.infradead.org On Friday 15 May 2015 12:43:34 Thierry Reding wrote: > On Wed, May 13, 2015 at 06:09:20PM +0200, Arnd Bergmann wrote: > > On Wednesday 13 May 2015 15:49:39 Thierry Reding wrote: > > > ARM: tegra: Devicetree changes for v4.2-rc1 > > > > > > Contains a couple of fixes and additions to device tree files. The most > > > notable change is a fix for a misapplied patch that was only exposed by > > > a recent change in the regulator subsystem that caused USB to break on > > > Tegra124 recently. > > > > It sounds like I should merge commit a4b6916cb35 ("ARM: tegra: Correct > > which USB controller has the UTMI pad registers") into the 4.1 fixes > > branch as well. Please confirm. > > I think you already did. I sent out a pull request for that not very > long ago and I must have forgotten to drop this patch from the Tegra > tree after it got applied to arm-soc. The merge commit for this in > the fixes branch is here: > > https://git.kernel.org/cgit/linux/kernel/git/arm/arm-soc.git/commit/?h=fixes&id=155171274d1dd9d9e5a012bd912c592402aa31d2 > > Hopefully git will be able to merge these together without conflicts. > Sorry about the dupe. > Everything is fine. Since both branches have the same commit ID, git can figure out how to do the merges. It would only be annoying to get the same patch with two different commit IDs. Ideally, your pull request would mention this kind of situation, so I don't need to ask or research myself about it. Arnd