From: Arnd Bergmann <arnd@arndb.de>
To: Roland Stigge <stigge@antcom.de>
Cc: arm@kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Defconfig update for LPC32xx
Date: Sat, 21 Apr 2012 11:46:29 +0000 [thread overview]
Message-ID: <201204211146.29929.arnd@arndb.de> (raw)
In-Reply-To: <1335006394-26810-1-git-send-email-stigge@antcom.de>
On Saturday 21 April 2012, Roland Stigge wrote:
> This patch updates the defconfig for the LPC32xx SoC after device tree
> conversion:
>
> * Adjustment to DT conversion, added new driver support
> * Added IPv6
> * Increased kernel log buffer
>
> Signed-off-by: Roland Stigge <stigge@antcom.de>
>
Hi Roland,
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?
Arnd
next prev parent reply other threads:[~2012-04-21 11:46 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 [this message]
2012-04-21 12:31 ` Roland Stigge
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=201204211146.29929.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=arm@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stigge@antcom.de \
/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