Thread (10 messages) 10 messages, 5 authors, 2011-02-04

Re: linux-next: manual merge of the msm tree with the arm tree

From: Greg KH <hidden>
Date: 2011-02-02 19:44:10
Also in: lkml

Possibly related (same subject, not in this thread)

On Wed, Feb 02, 2011 at 10:29:14AM -0800, David Brown wrote:
On Sun, Jan 30 2011, Stephen Rothwell wrote:
quoted
Hi David,

Today's linux-next merge of the msm tree got conflicts in
arch/arm/mach-msm/board-msm7x27.c, arch/arm/mach-msm/board-msm7x30.c,
arch/arm/mach-msm/board-qsd8x50.c and arch/arm/mach-msm/board-sapphire.c
between commit eda53d6d032effb653410b79e1b49e652a881744 ("ARM: P2V: avoid
initializers and assembly using PHYS_OFFSET") from the arm tree and
commit 07a3cc4814f790354d4c7be2c9dc6143a714a07a ("msm: Clean up useless
ifdefs") from the msm tree.

I fixed it up (see below) and can carry the fix as necessary.
What is the best way to resolve this?  I can't really merge against
Russell's tree, since he may need to rebase his tree before the merge
window?
Public trees should never be rebased, so that shouldn't happen.

thanks,

greg k-h
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help