public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Gortmaker <paul.gortmaker@windriver.com>
To: Bob Liu <lliubbo@gmail.com>
Cc: Lars-Peter Clausen <lars@metafoo.de>,
	Mike Frysinger <vapier@gentoo.org>,
	Sonic Zhang <sonic.zhang@analog.com>,
	<uclinux-dist-devel@blackfin.uclinux.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] blackfin: Fixup export.h includes
Date: Fri, 11 Nov 2011 10:53:53 -0500	[thread overview]
Message-ID: <4EBD4511.8010800@windriver.com> (raw)
In-Reply-To: <CAA_GA1cqV9aRtWwrTCG_Yu54js+DnCMeUE94xuN6+_9YTfmX5w@mail.gmail.com>

On 11-11-11 05:54 AM, Bob Liu wrote:
> On Fri, Nov 11, 2011 at 6:06 PM, Lars-Peter Clausen <lars@metafoo.de> wrote:
>> Commit 8dc7a9c84 ("blackfin: Add export.h to files using
>> EXPORT_SYMBOL/THIS_MODULE") inserted some of the include statements into
>> sections protected by an unrelated #if CONFIG_... statement. This can cause,
>> depending on the configuration used, warnings like this one:
>>
>>        arch/blackfin/mach-bf537/boards/stamp.c:2940: warning: data definition has no type or storage class
>>        arch/blackfin/mach-bf537/boards/stamp.c:2940: warning: type defaults to ‘int’ in declaration of ‘EXPORT_SYMBOL’
>>        arch/blackfin/mach-bf537/boards/stamp.c:2940: warning: parameter names (without types) in function declaration
>>
>> This patch fixes it by moving the includes out of the #if protected sections.
>>
>> Signed-off-by: Lars-Peter Clausen <lars@metafoo.de>

[...]

>>
> 
> Thanks!  I'll pick it.
> 
> Acked-by: Bob Liu <lliubbo@gmail.com>

Looks fine to me as well.  I'm assuming it will make it in
tree via Bob, as per above.

Thanks,
Paul.

> 

  parent reply	other threads:[~2011-11-11 15:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-11 10:06 [PATCH] blackfin: Fixup export.h includes Lars-Peter Clausen
2011-11-11 10:54 ` Bob Liu
2011-11-11 14:50   ` Mike Frysinger
2011-11-11 15:53   ` Paul Gortmaker [this message]
2011-11-11 14:50 ` Mike Frysinger

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=4EBD4511.8010800@windriver.com \
    --to=paul.gortmaker@windriver.com \
    --cc=lars@metafoo.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lliubbo@gmail.com \
    --cc=sonic.zhang@analog.com \
    --cc=uclinux-dist-devel@blackfin.uclinux.org \
    --cc=vapier@gentoo.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