linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Randy Dunlap <rdunlap@xenotime.net>
Cc: linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Thomas Gleixner <tglx@linutronix.de>, Ingo Molnar <mingo@elte.hu>,
	"H. Peter Anvin" <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>
Subject: Re: linux-next: Tree for Mar 14 (printk)
Date: Thu, 15 Mar 2012 07:19:34 +1100	[thread overview]
Message-ID: <20120315071934.77f0af64a4c633c545d68ea4@canb.auug.org.au> (raw)
In-Reply-To: <4F60BFA6.2030804@xenotime.net>

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

On Wed, 14 Mar 2012 08:56:22 -0700 Randy Dunlap <rdunlap@xenotime.net> wrote:
>
> on x86_64:
> 
> kernel/printk.c:1230:5: error: redefinition of 'printk_sched'
> include/linux/printk.h:136:5: note: previous definition of 'printk_sched' was here

Caused by commit 3ccf3e830615 ("printk/sched: Introduce special
printk_sched() for those awkward moments") from the tip tree.  The
declaration in include/linux/printk.h has alternatives determined by
CONFIG_PRINTK, but the definition in kernel/printk.c is not so
protected ...

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
\

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

  reply	other threads:[~2012-03-14 20:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-14  7:19 linux-next: Tree for Mar 14 Stephen Rothwell
2012-03-14 15:56 ` linux-next: Tree for Mar 14 (printk) Randy Dunlap
2012-03-14 20:19   ` Stephen Rothwell [this message]
2012-03-15 11:35     ` [PATCH] printk: Make it compile with !CONFIG_PRINTK Peter Zijlstra
2012-03-15 15:44       ` Randy Dunlap
2012-03-14 17:02 ` [PATCH -next] staging: ozwpan depends on NET Randy Dunlap
2012-03-14 17:10   ` Chris Kelly

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=20120315071934.77f0af64a4c633c545d68ea4@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=peterz@infradead.org \
    --cc=rdunlap@xenotime.net \
    --cc=tglx@linutronix.de \
    /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).