From: Steven Rostedt <rostedt@goodmis.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: linux-next: build warnings after merge of the ftrace tree
Date: Tue, 5 Jul 2016 15:29:09 -0400 [thread overview]
Message-ID: <20160705152909.726348af@gandalf.local.home> (raw)
In-Reply-To: <20160704154207.159b102a@canb.auug.org.au>
On Mon, 4 Jul 2016 15:42:07 +1000
Stephen Rothwell <sfr@canb.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
next prev parent reply other threads:[~2016-07-05 19:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-04 5:42 linux-next: build warnings after merge of the ftrace tree Stephen Rothwell
2016-07-05 19:29 ` Steven Rostedt [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-15 4:28 Stephen Rothwell
2022-01-15 9:55 ` Daniel Bristot de Oliveira
2023-01-30 5:51 Stephen Rothwell
2023-01-30 18:51 ` Steven Rostedt
2023-01-31 8:24 ` Bagas Sanjaya
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160705152909.726348af@gandalf.local.home \
--to=rostedt@goodmis.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox