From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-next] make s5p64x0_defconfig build error
Date: Wed, 14 Dec 2011 23:54:36 +0000 [thread overview]
Message-ID: <20111214235436.GG14542@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4EE93185.9030502@solonet.org.ua>
On Thu, Dec 15, 2011 at 01:30:13AM +0200, Denis Kuzmenko wrote:
> 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?
Most of the completed changes are in linux-next for the restart changes.
I have some additional commits (which were posted to the list as the 3rd
sub-series), which I'm not planning to submit in their current form -
they move things _towards_ sorting out the samsung stuff, but they're
all incomplete. These continue to be a part of my 'reset' branch.
Basically, the comments in the commit summary line marked with XXX need
addressing - and folk need to get out of the habbit of thinking "it's
an include file, it must go into somewhere called 'include'." Instead,
put includes local to a set of files in a directory in that same
directory.
Author: Russell King <rmk+kernel@arm.linux.org.uk>
Date: Sun Nov 6 16:22:23 2011 +0000
ARM: restart: plat-samsung: remove plat/reset.h and s5p_reset_hook
Now that s5p_reset_hook is unused, we can get rid of plat/reset.h and
the s5p_reset_hook code in plat/system-reset.h.
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Author: Russell King <rmk+kernel@arm.linux.org.uk>
Date: Sun Nov 6 16:20:11 2011 +0000
ARM: restart: s5pv210: use new restart hook XXX WIP XXX WHY IS THERE NO LOCAL HEADERS IN arch/arm/mach-exynos4 XXX
Hook these platforms restart code into the new restart hook rather
than using arch_reset().
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Author: Russell King <rmk+kernel@arm.linux.org.uk>
Date: Sun Nov 6 13:24:20 2011 +0000
ARM: restart: exynos4: use new restart hook XXX WIP XXX WHY IS THERE NO LOCAL HEADERS IN arch/arm/mach-exynos4 XXX
Hook these platforms restart code into the new restart hook rather
than using arch_reset().
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
next prev parent reply other threads:[~2011-12-14 23:54 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 [this message]
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=20111214235436.GG14542@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).