From mboxrd@z Thu Jan 1 00:00:00 1970 From: Greg KH Subject: Re: linux-next: manual merge of the usb tree with the s5p tree Date: Wed, 13 Apr 2011 21:52:24 -0700 Message-ID: <20110414045224.GB19370@kroah.com> References: <20110414141526.e0d5efa1.sfr@canb.auug.org.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from kroah.org ([198.145.64.141]:40981 "EHLO coco.kroah.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752802Ab1DNEvW (ORCPT ); Thu, 14 Apr 2011 00:51:22 -0400 Content-Disposition: inline In-Reply-To: <20110414141526.e0d5efa1.sfr@canb.auug.org.au> Sender: linux-next-owner@vger.kernel.org List-ID: To: Stephen Rothwell Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org, Joonyoung Shim , Kyungmin Park , Kukjin Kim On Thu, Apr 14, 2011 at 02:15:26PM +1000, Stephen Rothwell wrote: > Hi Greg, > > Today's linux-next merge of the usb tree got a conflict in > arch/arm/mach-exynos4/mach-nuri.c between commit d2a852f78de6 ("ARM: > EXYNOS4: Add Atmel mXT touchscreen device to the NURI board") from the > s5p tree and commit 01da92f7f643 ("ARM: EXYNOS4: Add usb ehci device to > the NURI board") from the usb tree. > > I fixed it up (see below) and can carry the fix as necessary. Thanks, the fix looks fine, I knew something like this would happen, and it would be easy to handle the merge. thanks, greg k-h