linux-next: manual merge of the suspend tree with the mips tree

2 messages, 2 authors, 2011-05-11 · open the first message on its own page

linux-next: manual merge of the suspend tree with the mips tree

From: Stephen Rothwell <hidden>
Date: 2011-05-11 03:13:59

Hi Rafael,

Today's linux-next merge of the suspend tree got a conflict in
arch/mips/alchemy/common/dbdma.c between commit 02810a022fd9 ("MIPS:
Alchemy: Convert dbdma.c to syscore_ops") from the mips tree and commit
4d0fb1376519 ("PM / MIPS: Use struct syscore_ops instead of sysdevs for
PM (v2)") from the suspend tree.

These seem to be trying to do the same thing.  I used the version from
the mips tree for now.  Please sort this out ...

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

Re: linux-next: manual merge of the suspend tree with the mips tree

From: Rafael J. Wysocki <hidden>
Date: 2011-05-11 19:31:35

On Wednesday, May 11, 2011, Stephen Rothwell wrote:
Hi Rafael,

Today's linux-next merge of the suspend tree got a conflict in
arch/mips/alchemy/common/dbdma.c between commit 02810a022fd9 ("MIPS:
Alchemy: Convert dbdma.c to syscore_ops") from the mips tree and commit
4d0fb1376519 ("PM / MIPS: Use struct syscore_ops instead of sysdevs for
PM (v2)") from the suspend tree.

These seem to be trying to do the same thing.  I used the version from
the mips tree for now.  Please sort this out ...
OK, I will drop the MIPS chanages from my tree.

Thanks,
Rafael
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help