From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCHv2 0/5] Misc picoxcell updates for 3.3
Date: Sat, 17 Dec 2011 21:18:25 +0100 [thread overview]
Message-ID: <18144957.3Nv7HuJyz7@wuerfel> (raw)
In-Reply-To: <1324129357-16030-1-git-send-email-jamie@jamieiles.com>
On Saturday 17 December 2011 13:42:32 Jamie Iles wrote:
> Here's v2 of a small series of feature updates for picoxcell in 3.3.
>
> Jamie
>
> Jamie Iles (5):
> ARM: picoxcell: remove mach/memory.h
> ARM: picoxcell: don't reserve irq_descs
> ARM: picoxcell: move io mappings to common.c
> MAINTAINERS: add maintainer entry for Picochip picoxcell
> ARM: picoxcell: implement watchdog restart
Hi Jamie,
The series looks good to me, aside from the trivial comments I've given
on patch 5. When you submit these for inclusion in arm-soc, please split
the series so that the first four patches can go into the next/cleanup
branch, while the last patch goes into the devel branch.
Arnd
prev parent reply other threads:[~2011-12-17 20:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-17 13:42 [PATCHv2 0/5] Misc picoxcell updates for 3.3 Jamie Iles
2011-12-17 13:42 ` [PATCHv2 1/5] ARM: picoxcell: remove mach/memory.h Jamie Iles
2011-12-17 13:42 ` [PATCHv2 2/5] ARM: picoxcell: don't reserve irq_descs Jamie Iles
2011-12-17 13:42 ` [PATCHv2 3/5] ARM: picoxcell: move io mappings to common.c Jamie Iles
2011-12-17 13:42 ` [PATCHv2 4/5] MAINTAINERS: add maintainer entry for Picochip picoxcell Jamie Iles
2011-12-17 13:42 ` [PATCHv2 5/5] ARM: picoxcell: implement watchdog restart Jamie Iles
2011-12-17 20:17 ` Arnd Bergmann
2011-12-18 0:05 ` Jamie Iles
2011-12-18 8:13 ` Russell King - ARM Linux
2011-12-18 9:41 ` Jamie Iles
2011-12-17 20:18 ` Arnd Bergmann [this message]
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=18144957.3Nv7HuJyz7@wuerfel \
--to=arnd@arndb.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).