linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
	Gleb Natapov <gleb@redhat.com>,
	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: build warning after merge of the moduleh tree
Date: Tue, 11 Oct 2011 09:16:18 -0400	[thread overview]
Message-ID: <20111011131618.GV19986@windriver.com> (raw)
In-Reply-To: <20111011202142.4d18840463055a8bdb9d1590@canb.auug.org.au>

[linux-next: build warning after merge of the moduleh tree] On 11/10/2011 (Tue 20:21) Stephen Rothwell wrote:

> Hi Paul,
> 
> After merging the moduleh tree, today's linux-next build (i386 defconfig)
> produced this warning:
> 
> arch/x86/kernel/cpu/perf_event_intel.c:1323:1: warning: data definition has no type or storage class [enabled by default]
> arch/x86/kernel/cpu/perf_event_intel.c:1323:1: warning: type defaults to 'int' in declaration of 'EXPORT_SYMBOL_GPL' [-Wimplicit-int]
> arch/x86/kernel/cpu/perf_event_intel.c:1323:1: warning: parameter names (without types) in function declaration [enabled by default]
> 
> Introduced by commit 144d31e6f190 ("perf, intel: Use GO/HO bits in
> perf-ctr") from the tip tree interacting with the module.h slipt up.
> 
> I'll add a patch tomorrow to add an include of export.h to this file.

Hi Stephen,

I've added this and the other nmi export to the post-merge queue.  I'll
assume for the moment that the regulator tree will pick up the 3rd one,
like you recommended.

Thanks,
Paul.

> -- 
> Cheers,
> Stephen Rothwell                    sfr@canb.auug.org.au
> http://www.canb.auug.org.au/~sfr/

  reply	other threads:[~2011-10-11 13:17 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-11  9:21 linux-next: build warning after merge of the moduleh tree Stephen Rothwell
2011-10-11 13:16 ` Paul Gortmaker [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-09-28  7:18 Stephen Rothwell
2011-09-28  7:39 ` Pihet-XID, Jean
2011-08-18  5:09 Stephen Rothwell
2011-08-18  8:26 ` Rafael J. Wysocki
2011-08-18  9:27   ` Stephen Rothwell
2011-08-18 20:57     ` Rafael J. Wysocki
2011-08-01  3:23 Stephen Rothwell
2011-08-02  7:26 ` Jens Axboe
2011-08-02  8:35   ` Stephen Rothwell
2011-08-02  8:42     ` Jens Axboe

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=20111011131618.GV19986@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=gleb@redhat.com \
    --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=sfr@canb.auug.org.au \
    --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).