linux-kernel - linux-next: manual merge of the nios2 tree with Linus' 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>] [day] [month] [year] [list]

Message-ID: <20180824091843.66cdda06@canb.auug.org.au>
Date:   Fri, 24 Aug 2018 09:18:43 +1000
From:   Stephen Rothwell <sfr@...b.auug.org.au>
To:     Ley Foon Tan <lftan@...era.com>
Cc:     Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Christoph Hellwig <hch@....de>,
        Masahiro Yamada <yamada.masahiro@...ionext.com>,
        Tobias Klauser <tklauser@...tanz.ch>
Subject: linux-next: manual merge of the nios2 tree with Linus' tree

Hi all,

Today's linux-next merge of the nios2 tree got a conflict in:

  arch/nios2/Kconfig.debug

between commit:

  06ec64b84c35 ("Kconfig: consolidate the "Kernel hacking" menu")

from Linus' tree and commit:

  93bdd8902339 ("nios2: kconfig: remove duplicate DEBUG_STACK_USAGE symbol defintions")

from the nios2 tree.

I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging.  You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.

-- 
Cheers,
Stephen Rothwell

diff --cc arch/nios2/Kconfig.debug
index 7a49f0d28d14,2ee8d5144c15..000000000000
--- a/arch/nios2/Kconfig.debug
+++ b/arch/nios2/Kconfig.debug
@@@ -3,15 -4,8 +3,6 @@@
  config TRACE_IRQFLAGS_SUPPORT
  	def_bool y
  
- config DEBUG_STACK_USAGE
- 	bool "Enable stack utilization instrumentation"
- 	depends on DEBUG_KERNEL
- 	help
- 	  Enables the display of the minimum amount of free stack which each
- 	  task has ever had available in the sysrq-T and sysrq-P debug output.
- 
- 	  This option will slow down process creation somewhat.
 -source "lib/Kconfig.debug"
--
  config EARLY_PRINTK
  	bool "Activate early kernel debugging"
  	default y

Content of type "application/pgp-signature" skipped