From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Kukjin Kim <kgene.kim@samsung.com>
Cc: linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
'Arnd Bergmann' <arnd@arndb.de>
Subject: Re: [GIT PULL] Samsung devel-2 for v3.2
Date: Thu, 6 Oct 2011 00:05:17 +0100 [thread overview]
Message-ID: <20111005230516.GA30439@sirena.org.uk> (raw)
In-Reply-To: <20111005165401.GA7155@opensource.wolfsonmicro.com>
On Wed, Oct 05, 2011 at 05:54:02PM +0100, Mark Brown wrote:
> On Tue, Oct 04, 2011 at 09:45:16PM +0900, Kukjin Kim wrote:
> > Could you please test on Cragganmore board again only with my for-next-test
> > branch?
> I tried this, same result as -next. v3.1-rc8 works fine. I also tried
> a bisect which was a bit of a nightmare due to soc_is_ and S5P_VA_GPIOn
> not being defined in the GPIO code and other places in a lot of
> revisions so I didn't finish it, perhaps later.
I also meant to say that I tried printascii() also and it didn't seem to
produce any additional logging. I'll complete the bisect and poke a bit
more tomorrow.
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: Thu, 6 Oct 2011 00:05:17 +0100 [thread overview]
Message-ID: <20111005230516.GA30439@sirena.org.uk> (raw)
In-Reply-To: <20111005165401.GA7155@opensource.wolfsonmicro.com>
On Wed, Oct 05, 2011 at 05:54:02PM +0100, Mark Brown wrote:
> On Tue, Oct 04, 2011 at 09:45:16PM +0900, Kukjin Kim wrote:
> > Could you please test on Cragganmore board again only with my for-next-test
> > branch?
> I tried this, same result as -next. v3.1-rc8 works fine. I also tried
> a bisect which was a bit of a nightmare due to soc_is_ and S5P_VA_GPIOn
> not being defined in the GPIO code and other places in a lot of
> revisions so I didn't finish it, perhaps later.
I also meant to say that I tried printascii() also and it didn't seem to
produce any additional logging. I'll complete the bisect and poke a bit
more tomorrow.
next prev parent reply other threads:[~2011-10-05 23:05 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
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 [this message]
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=20111005230516.GA30439@sirena.org.uk \
--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.