From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: linux-next ARM multi-platform randconfig errors
Date: Fri, 19 Apr 2013 22:58:36 +0200 [thread overview]
Message-ID: <201304192258.36276.arnd@arndb.de> (raw)
In-Reply-To: <20130419204028.GU10155@atomide.com>
On Friday 19 April 2013, Tony Lindgren wrote:
> Yeah. Here's an initial patch of what I had in mind, seems to
> do the trick. Will spend a little more time looking at it.
I suspect it won't be enough, as the same bugs you see with all of
them disable will likely happen also when you disable most of them.
If I'm right, the only solution is to look at each symbol individually
to find out exactly what code provides that symbol and ensure it
does not get used otherwise.
Arnd
next prev parent reply other threads:[~2013-04-19 20:58 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 3:06 linux-next ARM multi-platform randconfig errors Rob Herring
2013-04-19 16:12 ` Tony Lindgren
2013-04-19 16:41 ` Tomi Valkeinen
2013-04-19 19:43 ` Tony Lindgren
2013-04-19 19:51 ` Tony Lindgren
2013-04-19 20:11 ` Arnd Bergmann
2013-04-19 20:40 ` Tony Lindgren
2013-04-19 20:58 ` Arnd Bergmann [this message]
[not found] ` <20130419215134.GY10155@atomide.com>
2013-04-19 22:08 ` Arnd Bergmann
2013-04-19 22:53 ` Paul Walmsley
2013-04-19 21:02 ` Tony Lindgren
2013-04-19 21:09 ` Tony Lindgren
2013-04-19 19:52 ` Jon Hunter
2013-04-19 20:42 ` Tony Lindgren
2013-04-19 17:23 ` Tony Lindgren
2013-04-22 7:23 ` Roger Quadros
2013-04-22 8:21 ` Felipe Balbi
2013-04-22 11:52 ` Felipe Balbi
2013-04-22 12:45 ` Kishon Vijay Abraham I
2013-04-22 13:04 ` Felipe Balbi
2013-04-22 17:32 ` Mikulas Patocka
2013-04-22 22:57 ` Rob Herring
2013-05-13 22:37 ` [PATCH] bcache: Fix link errors on ARM Mikulas Patocka
2013-05-13 22:37 ` Mikulas Patocka
2013-04-22 18:59 ` linux-next ARM multi-platform randconfig errors Mike Turquette
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=201304192258.36276.arnd@arndb.de \
--to=arnd@arndb.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.