From: heiko@sntech.de (Heiko Stübner)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-next] make s5p64x0_defconfig build error
Date: Thu, 15 Dec 2011 09:09:25 +0100 [thread overview]
Message-ID: <201112150909.26229.heiko@sntech.de> (raw)
In-Reply-To: <CAF+7xWn80ZsgBNS80f0JYUXx2KN3VGM-Y2EOba7OLMwMGNfbKg@mail.gmail.com>
Am Donnerstag, 15. Dezember 2011, 00:54:58 schrieb Axel Lin:
> Hi Kukjin,
>
> > Axel and Will, thanks for pointing out.
> >
> > Oops, I couldn't have much time to follow up :(
> > But let me look at that in this weekend and I know, it can be escaped
> > before merge window :)
>
> I also found the same build errors by:
> make s5pc100_defconfig
> make s5pv210_defconfig
> make exynos4_defconfig
make s3c2410_defconfig
also produces the build errors
Heiko
next prev parent reply other threads:[~2011-12-15 8:09 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
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 [this message]
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=201112150909.26229.heiko@sntech.de \
--to=heiko@sntech.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).