linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nicholas Piggin <npiggin@gmail.com>
To: Larry Finger <Larry.Finger@lwfinger.net>
Cc: Russell King <rmk+kernel@armlinux.org.uk>,
	Michal Marek <mmarek@suse.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linuxppc-dev <linuxppc-dev@ozlabs.org>
Subject: Re: Build warning on 32-bit PPC - bisected to commit 989cea5c14be
Date: Thu, 22 Dec 2016 12:02:24 +1000	[thread overview]
Message-ID: <20161222120224.36202396@roar.ozlabs.ibm.com> (raw)
In-Reply-To: <53d94073-6e7e-af83-a29a-e811ab5fd802@lwfinger.net>

On Wed, 21 Dec 2016 13:49:07 -0600
Larry Finger <Larry.Finger@lwfinger.net> wrote:

> I am getting the following warning when I build kernel 4.9-git on my PowerBook 
> G4 with a 32-bit PPC processor:
> 
>    AS      arch/powerpc/kernel/misc_32.o
> arch/powerpc/kernel/misc_32.S:299:7: warning: "CONFIG_FSL_BOOKE" is not defined 
> [-Wundef]
> 
> This problem has been bisected to commit 989cea5c14be ("kbuild: prevent 
> lib-ksyms.o rebuilds").
> 
> Thanks,
> 
> Larry

Hi Larry,

This is strange you've bisected it there, I can't see how that patch would
trigger it. That said, powerpc has had a few small build system glitches.

It looks like this warning could be fixed by changing #elif CONFIG_FSL_BOOKE
to #elif defined (CONFIG_FSL_BOOKE). Want to send a patch (if it works)?

Thanks,
Nick

  reply	other threads:[~2016-12-22  2:02 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-21 19:49 Build warning on 32-bit PPC - bisected to commit 989cea5c14be Larry Finger
2016-12-22  2:02 ` Nicholas Piggin [this message]
2016-12-22 14:53   ` Larry Finger

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=20161222120224.36202396@roar.ozlabs.ibm.com \
    --to=npiggin@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=mmarek@suse.com \
    --cc=rmk+kernel@armlinux.org.uk \
    /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).