linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: Latest build results - errors/warnings - lots of them
Date: Tue, 30 Apr 2013 17:22:57 -0700	[thread overview]
Message-ID: <20130501002257.GH28721@atomide.com> (raw)
In-Reply-To: <20130430235147.GG28721@atomide.com>

* Tony Lindgren <tony@atomide.com> [130430 16:57]:
> * Arnd Bergmann <arnd@arndb.de> [130430 16:16]:
> > 
> > I've uploaded this to the test-merge-20130430 branch in the arm-soc
> > tree if anyone is curious. I suppose we should get all the changes
> > in arch/arm included in the merge window and then work with the
> > subsystem maintainers on the other bugs.
> 
> >  arch/arm/mach-omap2/Kconfig                   | 133 +++++++++++++-------------
> >  arch/arm/mach-omap2/Makefile                  |   8 +-
> 
> Nice, I like your changes to flip ARCH_OMAP2PLUS to be selected
> by the SoC. That's a better way to fix things than just tinkering
> with the Makefile like I posted earlier today.
> 
> Now you have SOC_OMAP5 selected twice in omap2plus_defconfig though,
> which causes:
> 
> .config:283:warning: override: reassigning to symbol SOC_OMAP5
> 
> For the SERIAL_OMAP change, let's just use my earlier patch
> "ARM: OMAP2+: Fix unmet direct dependencies for SERIAL_OMAP".
> We should not select optional drivers at all in Kconfig.

And looks like also the following should be folded in to allow building
ARCH_OMAP2. Other than that your branch seems to build & boot
fine on omaps.

Regards,

Tony


--- a/arch/arm/configs/omap2plus_defconfig
+++ b/arch/arm/configs/omap2plus_defconfig
@@ -21,6 +21,7 @@ CONFIG_MODVERSIONS=y
 CONFIG_MODULE_SRCVERSION_ALL=y
 # CONFIG_BLK_DEV_BSG is not set
 CONFIG_ARCH_OMAP2=y
+CONFIG_ARCH_MULTI_V6=y
 CONFIG_ARCH_OMAP3=y
 CONFIG_ARCH_OMAP4=y
 CONFIG_SOC_OMAP5=y

  reply	other threads:[~2013-05-01  0:22 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-30  8:17 Latest build results - errors/warnings - lots of them Russell King - ARM Linux
2013-04-30 11:04 ` Arnd Bergmann
2013-04-30 11:43   ` Dave Martin
2013-04-30 11:54     ` Arnd Bergmann
2013-04-30 15:12     ` Nicolas Pitre
2013-04-30 17:28       ` Dave Martin
2013-04-30 18:18         ` Nicolas Pitre
2013-05-02  8:34           ` Russell King - ARM Linux
2013-05-02  9:46             ` Russell King - ARM Linux
2013-05-02 10:40               ` Dave Martin
2013-04-30 16:11   ` Tony Lindgren
2013-04-30 21:49     ` Tony Lindgren
2013-05-02  6:02   ` Shawn Guo
2013-04-30 23:11 ` Arnd Bergmann
2013-04-30 23:51   ` Tony Lindgren
2013-05-01  0:22     ` Tony Lindgren [this message]
2013-05-02  8:22 ` Russell King - ARM Linux
2013-05-02 15:38   ` Tony Lindgren
2013-05-02 17:07     ` Eduardo Valentin
2013-05-02 18:03       ` Arnd Bergmann
2013-05-02 18:45         ` Eduardo Valentin
2013-05-02 18:06       ` Felipe Balbi
2013-05-02 18:46         ` Eduardo Valentin
2013-05-02 18:54     ` Russell King - ARM Linux
2013-05-06  2:40     ` NeilBrown
2013-05-08 22:17       ` Tony Lindgren

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=20130501002257.GH28721@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).