Thread (4 messages) 4 messages, 3 authors, 2011-06-23

Re: linux-next: manual merge of the m68knommu tree with the m68k tree

From: Greg Ungerer <hidden>
Date: 2011-06-22 06:37:48
Also in: lkml

Hi Stephen,

On 22/06/11 11:12, Stephen Rothwell wrote:
Today's linux-next merge of the m68knommu tree got a conflict in
arch/m68k/include/asm/bitops_mm.h between commit 17c74432b88e
("m68k/bitops: Make bitmap data pointer of atomic ops volatile") from the
m68k tree and commit 2cb0d89e66b1 ("m68k: merge mmu and non-mmu
bitops.h") from the m68knommu tree.

The latter effectively deletes in the file and in doing the merge,
removes the funtions that were modified by the former commit.  So I just
removed the file.
That would be right. The changes that Geert's patch makes are in
my merge patch.

Geert: do you want me to hold of on merging the bitops.h files?

Regards
Greg


-- 
------------------------------------------------------------------------
Greg Ungerer  --  Principal Engineer        EMAIL:     gerg@snapgear.com
SnapGear Group, McAfee                      PHONE:       +61 7 3435 2888
8 Gardner Close                             FAX:         +61 7 3217 5323
Milton, QLD, 4064, Australia                WEB: http://www.SnapGear.com
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help