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

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 9 Nov 2011 11:15:19 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Greg Ungerer <gerg@...pgear.com>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Geert Uytterhoeven <geert@...ux-m68k.org>
Subject: linux-next: manual merge of the m68knommu tree with the m68k tree

Hi Greg,

Today's linux-next merge of the m68knommu tree got a conflict in
arch/m68k/Kconfig between commit d890d7399525 ("m68k/irq: Remove obsolete
m68k irq framework") from the m68k tree and commit 4e8a9e70dfe8 ("m68k:
selection of GENERIC_ATOMIC64 is not MMU specific") from the m68knommu
tree.

Just context changes.  I fixed it up (see below) and can carry the fix as
necessary.
-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

diff --cc arch/m68k/Kconfig
index 361d540,26ed01b..0000000
--- a/arch/m68k/Kconfig
+++ b/arch/m68k/Kconfig
@@@ -3,9 -3,8 +3,8 @@@ config M68
  	default y
  	select HAVE_IDE
  	select HAVE_AOUT if MMU
- 	select GENERIC_ATOMIC64 if MMU
 -	select HAVE_GENERIC_HARDIRQS if !MMU
 -	select GENERIC_IRQ_SHOW if !MMU
 +	select HAVE_GENERIC_HARDIRQS
 +	select GENERIC_IRQ_SHOW
  	select ARCH_HAVE_NMI_SAFE_CMPXCHG if RMW_INSNS
  
  config RWSEM_GENERIC_SPINLOCK

Content of type "application/pgp-signature" skipped