linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: stigge@antcom.de (Roland Stigge)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] Defconfig update for LPC32xx
Date: Sat, 21 Apr 2012 14:31:10 +0200	[thread overview]
Message-ID: <4F92A88E.1000007@antcom.de> (raw)
In-Reply-To: <201204211146.29929.arnd@arndb.de>

Hi Arnd,

On 21/04/12 13:46, Arnd Bergmann wrote:
> I think the latest version of all of your patches is good, but I've
> lost track of which ones you want to go through arm-soc. Can you send
> me pull requests for each series you want applied on monday if you get
> no more comments?

Yes, I was planning an arm-soc pull request anyway. First concentrating
on the other subsystem's patches and then providing the arm-soc bits in
one go. The other subsystem's patches are not merged completely, yet,
but arm-soc can already merge on monday - pretty stabilized DT
conversion now.

Thanks,

Roland

      reply	other threads:[~2012-04-21 12:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-21 11:06 [PATCH] Defconfig update for LPC32xx Roland Stigge
2012-04-21 11:46 ` Arnd Bergmann
2012-04-21 12:31   ` Roland Stigge [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=4F92A88E.1000007@antcom.de \
    --to=stigge@antcom.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).