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 09:11:04 -0700	[thread overview]
Message-ID: <20130430161104.GB26257@atomide.com> (raw)
In-Reply-To: <201304301304.20650.arnd@arndb.de>

* Arnd Bergmann <arnd@arndb.de> [130430 04:10]:
> On Tuesday 30 April 2013, Russell King - ARM Linux wrote:
> > Latest nightly build of 3.9+my for-next+arm-soc's for-next results in a
> > great load of new warnings and errors.  arch/arm/common/mcpm_head.S,
> > arch/arm/common/mcpm_platsmp.c, arch/arm/common/vlock.S are the biggest
> > source of errors.
> 
> Yes, I noticed this but haven't gotten around to prepare a patch. I'll comment
> below.
> 
> > OMAP stuff needs a serious look at too - much Kconfig madness there
> > caused by over-use of select, which then goes on to cause build errors
> > because it assumes some stuff is always enabled.

I have posted a few randconfig fixes in "[PATCH 0/3] few omap randconfig
fixes for v3.10" that also remove the select of SERIAL_OMAP that I missed
while fixing the 8250 issue. I was planning to send a pull request after
the merge window, but can do it now too if people prefer that.
 
> Ack. I have not looked much at randconfig output, but this has certianly
> grown worse after CONFIG_ARCH_OMAP has gotten included in ARCH_MULTIPLATFORM

I have a patch coming for the "no SoC selected" randconfig issue as
discussed in the "linux-next ARM multi-platform randconfig errors"
thread. I suggest we do the minimal fix I already posted for now,
then reorganize more of the Makefile as Arnd suggested for v3.11.

Regards,

Tony

  parent reply	other threads:[~2013-04-30 16:11 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 [this message]
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
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=20130430161104.GB26257@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).