linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Steven Rostedt <rostedt@goodmis.org>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Jiri Kosina <jkosina@suse.cz>, Petr Mladek <pmladek@suse.cz>,
	"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Subject: linux-next: build failure after merge of the ftrace tree
Date: Fri, 21 Nov 2014 18:32:15 +1100	[thread overview]
Message-ID: <20141121183215.01ba539c@canb.auug.org.au> (raw)

[-- Attachment #1: Type: text/plain, Size: 1239 bytes --]

Hi Steven,

After merging the ftrace tree, today's linux-next build (powerpc
allnoconfig) failed like this:

In file included from include/asm-generic/percpu.h:6:0,
                 from arch/powerpc/include/asm/percpu.h:19,
                 from include/linux/percpu.h:11,
                 from include/linux/sched.h:41,
                 from arch/powerpc/kernel/asm-offsets.c:17:
include/linux/percpu.h:138:17: error: 'printk_func_t' undeclared here (not in a function)
 DECLARE_PER_CPU(printk_func_t, printk_func);
                 ^
include/linux/percpu-defs.h:101:38: note: in definition of macro 'DECLARE_PER_CPU_SECTION'
  extern __PCPU_ATTRS(sec) __typeof__(type) name
                                      ^
include/linux/percpu.h:138:1: note: in expansion of macro 'DECLARE_PER_CPU'
 DECLARE_PER_CPU(printk_func_t, printk_func);
 ^

Caused by commit afdc34a3d3b8 ("printk: Add per_cpu printk func to
allow printk to be diverted").  See Rule 1 in
Documentation/SubmitChecklist.

I reverted that commit (and the following one (a9edc8809328 "x86/nmi:
Perform a safe NMI stack trace on all CPUs" in case it depended in it)
for today.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

             reply	other threads:[~2014-11-21  7:32 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-21  7:32 Stephen Rothwell [this message]
2014-11-21 10:50 ` linux-next: build failure after merge of the ftrace tree Jiri Kosina
2014-11-21 14:20   ` Steven Rostedt
2014-11-21 14:23     ` Jiri Kosina
2014-11-21 14:27     ` Steven Rostedt
2014-11-21 12:43 ` Steven Rostedt
  -- strict thread matches above, loose matches on Subject: below --
2023-10-23  2:30 Stephen Rothwell
2023-10-23  3:32 ` Matthew Wilcox
2023-10-23 13:41   ` Steven Rostedt
2023-10-26  1:18 ` Stephen Rothwell
2023-10-26  1:21   ` Steven Rostedt
2022-01-12  0:31 Stephen Rothwell
2022-01-14  1:02 ` Stephen Rothwell
2022-01-14  1:04   ` Steven Rostedt
2022-01-14  2:16   ` Steven Rostedt
2022-01-14  2:58     ` Stephen Rothwell
2022-01-14  3:02       ` Stephen Rothwell
2022-01-14  3:25         ` Steven Rostedt
2022-01-14  3:34           ` Stephen Rothwell
2022-01-14  3:50             ` Steven Rostedt
2022-01-14  5:12               ` Yinan Liu
2022-01-14  6:42               ` Stephen Rothwell
2021-06-10  8:08 Stephen Rothwell
2021-06-10  8:26 ` Peter Zijlstra
2021-06-10 15:06   ` Steven Rostedt
2021-06-15  6:51     ` Mark-PK Tsai
2020-06-03  7:42 Stephen Rothwell
2020-06-03 15:10 ` Tom Zanussi
2020-06-03 15:22 ` Steven Rostedt
2020-06-03 15:24   ` Tom Zanussi
2020-06-03 15:30     ` Steven Rostedt
2020-06-03 21:49       ` Stephen Rothwell
2013-03-01  2:47 Stephen Rothwell
2013-03-01  3:06 ` Steven Rostedt
2013-03-02  2:45 ` Steven Rostedt
2013-03-02  3:42   ` Stephen Rothwell
2013-03-02  3:55     ` Steven Rostedt
2013-03-02  4:17       ` Stephen Rothwell
2013-03-02  4:22         ` Steven Rostedt
2013-03-02  4:55           ` Stephen Rothwell

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=20141121183215.01ba539c@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=jkosina@suse.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=pmladek@suse.cz \
    --cc=rostedt@goodmis.org \
    /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;
as well as URLs for NNTP newsgroup(s).