From: Olof Johansson <olof@lixom.net>
To: Arnd Bergmann <arnd@arndb.de>
Cc: Kukjin Kim <kgene.kim@samsung.com>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: Exynos regressions w.r.t. config and debuggability due to multiplatform
Date: Fri, 26 Apr 2013 17:37:17 -0700 [thread overview]
Message-ID: <20130427003717.GC2350@quad.lixom.net> (raw)
In-Reply-To: <201304251931.25028.arnd@arndb.de>
On Thu, Apr 25, 2013 at 07:31:24PM +0200, Arnd Bergmann wrote:
> On Thursday 25 April 2013, Kukjin Kim wrote:
> >
> > On 04/25/13 00:03, Arnd Bergmann wrote:
> > > On Wednesday 24 April 2013, Olof Johansson wrote:
> > >> I think we should hold off on multiplatform for exynos until it works
> > >> better, i.e. 3.11.
> > >>
> > I think, this would be better choice for now if it's not urgent...
> >
>
> I spent a lot of time on it because it's a priority for Linaro, but
> that means I'm biased in the question of whether to merge it or not.
> It should only get in if you and Olof think it's a good idea.
I've reverted the commit you pointed out as the problematic one now,
and with that I get a working setup. That means most of the base patches are
in, just not the final Kconfig shuffling. 3.11 seems more realistic for that.
-Olof
WARNING: multiple messages have this Message-ID (diff)
From: olof@lixom.net (Olof Johansson)
To: linux-arm-kernel@lists.infradead.org
Subject: Exynos regressions w.r.t. config and debuggability due to multiplatform
Date: Fri, 26 Apr 2013 17:37:17 -0700 [thread overview]
Message-ID: <20130427003717.GC2350@quad.lixom.net> (raw)
In-Reply-To: <201304251931.25028.arnd@arndb.de>
On Thu, Apr 25, 2013 at 07:31:24PM +0200, Arnd Bergmann wrote:
> On Thursday 25 April 2013, Kukjin Kim wrote:
> >
> > On 04/25/13 00:03, Arnd Bergmann wrote:
> > > On Wednesday 24 April 2013, Olof Johansson wrote:
> > >> I think we should hold off on multiplatform for exynos until it works
> > >> better, i.e. 3.11.
> > >>
> > I think, this would be better choice for now if it's not urgent...
> >
>
> I spent a lot of time on it because it's a priority for Linaro, but
> that means I'm biased in the question of whether to merge it or not.
> It should only get in if you and Olof think it's a good idea.
I've reverted the commit you pointed out as the problematic one now,
and with that I get a working setup. That means most of the base patches are
in, just not the final Kconfig shuffling. 3.11 seems more realistic for that.
-Olof
next prev parent reply other threads:[~2013-04-27 0:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 3:34 Exynos regressions w.r.t. config and debuggability due to multiplatform Olof Johansson
2013-04-24 3:34 ` Olof Johansson
2013-04-24 15:03 ` Arnd Bergmann
2013-04-24 15:03 ` Arnd Bergmann
2013-04-25 15:33 ` Kukjin Kim
2013-04-25 15:33 ` Kukjin Kim
2013-04-25 17:31 ` Arnd Bergmann
2013-04-25 17:31 ` Arnd Bergmann
2013-04-27 0:37 ` Olof Johansson [this message]
2013-04-27 0:37 ` Olof Johansson
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=20130427003717.GC2350@quad.lixom.net \
--to=olof@lixom.net \
--cc=arnd@arndb.de \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@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 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.