linux-kernel - linux-next: manual merge of the gpio tree with the xtensa 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]

Message-Id: <20140108151459.d4743129d9cae88865774073@canb.auug.org.au>
Date:	Wed, 8 Jan 2014 15:14:59 +1100
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Linus Walleij <linus.walleij@...aro.org>,
	Chris Zankel <chris@...kel.net>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Baruch Siach <baruch@...s.co.il>,
	Max Filippov <jcmvbkbc@...il.com>
Subject: linux-next: manual merge of the gpio tree with the xtensa tree

Hi Linus,

Today's linux-next merge of the gpio tree got a conflict in
arch/xtensa/Kconfig between commit dbacef090841 ("xtensa: add SMP
support") from the xtensa tree and commit a1a2bdec4772 ("gpio: xtensa:
depend on HAVE_XTENSA_GPIO32") from the gpio tree.

I fixed it up (see below) and can carry the fix as necessary (no action
is required).

-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

diff --cc arch/xtensa/Kconfig
index 70a160be3464,f8df0cc70cb6..000000000000
--- a/arch/xtensa/Kconfig
+++ b/arch/xtensa/Kconfig
@@@ -64,9 -64,9 +64,12 @@@ config MM
  config VARIANT_IRQ_SWITCH
  	def_bool n
  
 +config MAY_HAVE_SMP
 +	def_bool n
 +
+ config HAVE_XTENSA_GPIO32
+ 	def_bool n
+ 
  menu "Processor type and features"
  
  choice

Content of type "application/pgp-signature" skipped