linux-kernel - Re: linux-next: build warnings after merge of the ftrace 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-prev] [day] [month] [year] [list]

Message-ID: <20160705152909.726348af@gandalf.local.home>
Date:	Tue, 5 Jul 2016 15:29:09 -0400
From:	Steven Rostedt <rostedt@...dmis.org>
To:	Stephen Rothwell <sfr@...b.auug.org.au>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: linux-next: build warnings after merge of the ftrace tree

On Mon, 4 Jul 2016 15:42:07 +1000
Stephen Rothwell <sfr@...b.auug.org.au> wrote:

> Hi Steven,
> 
> After merging the ftrace tree, today's linux-next build (x86_64
> allmodconfig) produced these warnings:

I'm currently running the patch I posted previously and if all goes
well will have that patch added to my ftrace-next repo tonight.
Fengguang Wu's bot caught this, but I was working on something else.
Over the weekend I was wondering why I haven't pushed my repo yet (I
forgot about this), and pushed my branch.

So this doesn't happen again, I added:

 # CONFIG_SECTION_MISMATCH_WARN_ONLY is not set

to one of the configs I use for testing, as my tests didn't die when
a mismatch was added and caught.

-- Steve

Link: http://lkml.kernel.org/r/20160704102139.19cbc0d9@gandalf.local.home