Linux on ARM based TI OMAP SoCs
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: "Gadiyar, Anand" <gadiyar@ti.com>
Cc: linux-omap <linux-omap@vger.kernel.org>
Subject: Re: SMP_ON_UP? - Build break with custom minimal defconfig
Date: Tue, 21 Sep 2010 08:54:00 -0700	[thread overview]
Message-ID: <20100921155400.GR4611@atomide.com> (raw)
In-Reply-To: <AANLkTim-mQjFnqGo_G971yTbU9FLnUja2t_axytGM5LN@mail.gmail.com>

* Gadiyar, Anand <gadiyar@ti.com> [100921 08:41]:
> Hi all,
> 
> I was trying to use current linux-omap master to put together a custom
> minimal defconfig for a beagleboard, and I'm seeing a compile error:
> 
>   CC      init/main.o
> In file included from include/linux/highmem.h:9,
>                  from include/linux/pagemap.h:10,
>                  from include/linux/mempolicy.h:70,
>                  from init/main.c:50:
> /home/userdata/a0393673/kernels/tony/linux-omap-2.6/arch/arm/include/asm/cacheflush.h:
> In function '__flush_icache_all':
> /home/userdata/a0393673/kernels/tony/linux-omap-2.6/arch/arm/include/asm/cacheflush.h:332:
> error: implicit declaration of function '__flush_icache_preferred'
> make[1]: *** [init/main.o] Error 1
> make: *** [init] Error 2
> 
> I think this is related to the recent SMP_ON_UP patches.
> 
> The reduced .config I'm using (generated using `make savedefconfig`) is below.
> 
> I'll try and debug in a while, but just reporting for now.

Yes that sounds like a bug in a smp_on_up related patch. Will try your
defconfig here too.

Thanks,

Tony

  reply	other threads:[~2010-09-21 15:53 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-21 15:40 SMP_ON_UP? - Build break with custom minimal defconfig Gadiyar, Anand
2010-09-21 15:54 ` Tony Lindgren [this message]
2010-09-21 15:59   ` Gadiyar, Anand

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=20100921155400.GR4611@atomide.com \
    --to=tony@atomide.com \
    --cc=gadiyar@ti.com \
    --cc=linux-omap@vger.kernel.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