From: Denis Kuzmenko <linux@solonet.org.ua>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Will Deacon <will.deacon@arm.com>, Axel Lin <axel.lin@gmail.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-samsung-soc@vger.kernel.org"
<linux-samsung-soc@vger.kernel.org>,
Kukjin Kim <kgene.kim@samsung.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [linux-next] make s5p64x0_defconfig build error
Date: Thu, 15 Dec 2011 01:30:13 +0200 [thread overview]
Message-ID: <4EE93185.9030502@solonet.org.ua> (raw)
In-Reply-To: <20111214191205.GF14542@n2100.arm.linux.org.uk>
On 12/14/2011 09:12 PM, Russell King - ARM Linux wrote:
> On Wed, Dec 14, 2011 at 12:32:44PM +0000, Will Deacon wrote:
>> On Wed, Dec 14, 2011 at 04:57:10AM +0000, Axel Lin wrote:
> So... unless things change, we can expect Gemini, almost all Samsung
> stuff, shmobile, vt8500, and Telechips TCC8k to be at least broken at
> the next merge window.
Mini2440 march (s3c24xx platform) is not broken in v3.2-rc5. Does that
mean that s3c24xx is untouched by this issue or this means that I should
use linux-next?
If this problem is related to s3c24xx I'm ready to do my best for saving
that platform from being removed.
--
Best regards, Denis Kuzmenko.
next prev parent reply other threads:[~2011-12-14 23:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-14 4:57 [linux-next] make s5p64x0_defconfig build error Axel Lin
2011-12-14 12:32 ` Will Deacon
2011-12-14 19:12 ` Russell King - ARM Linux
2011-12-14 20:45 ` Nicolas Pitre
2011-12-14 23:30 ` Denis Kuzmenko [this message]
2011-12-14 23:54 ` Russell King - ARM Linux
2011-12-14 23:33 ` Kukjin Kim
2011-12-14 23:54 ` Axel Lin
2011-12-15 8:09 ` Heiko Stübner
2011-12-15 5:00 ` Mark Brown
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=4EE93185.9030502@solonet.org.ua \
--to=linux@solonet.org.ua \
--cc=axel.lin@gmail.com \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=will.deacon@arm.com \
/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