From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: 'Arnd Bergmann' <arnd@arndb.de>,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org
Subject: Re: [GIT PULL] Samsung devel-2 for v3.2
Date: Tue, 4 Oct 2011 13:59:17 +0100 [thread overview]
Message-ID: <20111004125916.GC6934@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <019201cc8293$7776a790$6663f6b0$%kim@samsung.com>
On Tue, Oct 04, 2011 at 09:45:16PM +0900, Kukjin Kim wrote:
> Mark Brown wrote:
> > As I reported the other day this change breaks the boot early on on the
> > Cragganmore S3C6410 based systems (I've not actually fired up my
> > SMDK6410 but I suspect it may have issues too). I did make some brief
> > attempts to debug but as there's no console output at all and the diff
> > is rather large it's not easy to see what's gone wrong.
> Could you please test on Cragganmore board again only with my for-next-test
> branch?
> (I have did 'git-revert' some patches which have some dependencies with
> other tree to build without others.)
Sure - it may be tomorrow morning (so late tomorrow your time) before
I'm sitting in front of a board for long enough to do it.
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [GIT PULL] Samsung devel-2 for v3.2
Date: Tue, 4 Oct 2011 13:59:17 +0100 [thread overview]
Message-ID: <20111004125916.GC6934@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <019201cc8293$7776a790$6663f6b0$%kim@samsung.com>
On Tue, Oct 04, 2011 at 09:45:16PM +0900, Kukjin Kim wrote:
> Mark Brown wrote:
> > As I reported the other day this change breaks the boot early on on the
> > Cragganmore S3C6410 based systems (I've not actually fired up my
> > SMDK6410 but I suspect it may have issues too). I did make some brief
> > attempts to debug but as there's no console output at all and the diff
> > is rather large it's not easy to see what's gone wrong.
> Could you please test on Cragganmore board again only with my for-next-test
> branch?
> (I have did 'git-revert' some patches which have some dependencies with
> other tree to build without others.)
Sure - it may be tomorrow morning (so late tomorrow your time) before
I'm sitting in front of a board for long enough to do it.
next prev parent reply other threads:[~2011-10-04 12:59 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-02 9:25 [GIT PULL] Samsung devel-2 for v3.2 Kukjin Kim
2011-10-02 9:25 ` Kukjin Kim
2011-10-02 19:29 ` Mark Brown
2011-10-02 19:29 ` Mark Brown
2011-10-03 3:27 ` Kukjin Kim
2011-10-03 3:27 ` Kukjin Kim
2011-10-03 10:36 ` Mark Brown
2011-10-03 10:36 ` Mark Brown
2011-10-03 11:22 ` Russell King - ARM Linux
2011-10-03 11:22 ` Russell King - ARM Linux
2011-10-03 12:16 ` Mark Brown
2011-10-03 12:16 ` Mark Brown
2011-10-07 17:56 ` Arnd Bergmann
2011-10-07 17:56 ` Arnd Bergmann
2011-10-07 19:14 ` Mark Brown
2011-10-07 19:14 ` Mark Brown
2011-10-10 4:27 ` Kukjin Kim
2011-10-10 4:27 ` Kukjin Kim
2011-10-20 12:57 ` Arnd Bergmann
2011-10-20 12:57 ` Arnd Bergmann
2011-10-04 12:45 ` Kukjin Kim
2011-10-04 12:45 ` Kukjin Kim
2011-10-04 12:59 ` Mark Brown [this message]
2011-10-04 12:59 ` Mark Brown
2011-10-05 16:54 ` Mark Brown
2011-10-05 16:54 ` Mark Brown
2011-10-05 23:05 ` Mark Brown
2011-10-05 23:05 ` Mark Brown
[not found] ` <00e601cc83f1$3298e660$97cab320$%kim@samsung.com>
[not found] ` <20111006155701.GA1470@opensource.wolfsonmicro.com>
2011-10-06 17:14 ` Mark Brown
2011-10-07 10:58 ` Kukjin Kim
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=20111004125916.GC6934@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--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.