From: ithamar.adema@team-embedded.nl (Ithamar R. Adema)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/10] Support for NXP LPC2K SoCs
Date: Sat, 02 Apr 2011 22:55:17 +0200 [thread overview]
Message-ID: <1301777717.2838.2.camel@team-embedded-2> (raw)
In-Reply-To: <1301394656-24853-1-git-send-email-ithamar.adema@team-embedded.nl>
Hi Russell,
On Tue, 2011-03-29 at 12:30 +0200, Ithamar R. Adema wrote:
> The following patch series implements support for the ARM7TDMI-S based
> NXP LPC2K System-on-Chips, and, as first board, the EmbeddedArtists
> LPC2478 Developer's Kit.
[snip]
Since there have been no further comments, can I send these patches to
your patch system or do you prefer to have a git repository to pull
from?
If there are still other things to take care of first, please let me
know and I'll try to take care of it.
Regards,
Ithamar.
next prev parent reply other threads:[~2011-04-02 20:55 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-29 10:30 [PATCH v4 0/10] Support for NXP LPC2K SoCs Ithamar R. Adema
2011-03-29 10:30 ` [PATCH v4 01/10] lpc2k: Core support Ithamar R. Adema
2011-03-29 10:30 ` [PATCH v4 02/10] lpc2k: Exception vector handling Ithamar R. Adema
2011-03-29 10:30 ` [PATCH v4 03/10] lpc2k: clk API Ithamar R. Adema
2011-03-29 10:30 ` [PATCH v4 04/10] lpc2k: generic time and clockevents Ithamar R. Adema
2011-03-29 10:30 ` [PATCH v4 05/10] lpc2k: gpiolib Ithamar R. Adema
2011-03-29 10:30 ` [PATCH v4 06/10] lpc2k: multifunction pin configuration Ithamar R. Adema
2011-03-29 10:30 ` [PATCH v4 08/10] lpc2k: Add UART, SSP, and MCI devices Ithamar R. Adema
2011-03-29 10:30 ` [PATCH v4 09/10] lpc2k: defconfig for NXP LPC2K platform Ithamar R. Adema
2011-03-29 10:30 ` [PATCH v4 10/10] NOMMU: implement access_remote_vm Ithamar R. Adema
2011-03-29 10:31 ` [PATCH v4 07/10] lpc2k: Add EmbeddedArtists LPC2478 Developer's Kit board Ithamar R. Adema
2011-04-02 20:55 ` Ithamar R. Adema [this message]
2011-04-04 23:50 ` [PATCH v4 0/10] Support for NXP LPC2K SoCs Kevin Wells
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=1301777717.2838.2.camel@team-embedded-2 \
--to=ithamar.adema@team-embedded.nl \
--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).