From: Shawn Guo <shawn.guo@freescale.com>
To: Bill Pringlemeir <bpringlemeir@nbsps.com>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] vf610-twr device updates
Date: Wed, 6 Aug 2014 17:11:21 +0800 [thread overview]
Message-ID: <20140806091120.GK2167@dragon> (raw)
In-Reply-To: <1407260041-19234-1-git-send-email-bpringlemeir@nbsps.com>
On Tue, Aug 05, 2014 at 01:33:59PM -0400, Bill Pringlemeir wrote:
> arch/arm/boot/dts/vf610-twr.dts | 17 ++++++++++++++---
> 1 file changed, 14 insertions(+), 3 deletions(-)
>
> [PATCH 1/2] ARM: dts: vf610-twr: Fix pinctrl_esdhc1 pin definitions.
> [PATCH 2/2] ARM: dts: vf610-twr: Add ttyLP2 device.
Applied both, thanks.
prev parent reply other threads:[~2014-08-06 9:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-05 17:33 [PATCH 0/2] vf610-twr device updates Bill Pringlemeir
2014-08-05 17:34 ` [PATCH 1/2] ARM: dts: vf610-twr: Fix pinctrl_esdhc1 pin definitions Bill Pringlemeir
2014-08-05 17:39 ` Bill Pringlemeir
2014-08-05 17:34 ` [PATCH 2/2] ARM: dts: vf610-twr: Add ttyLP2 device Bill Pringlemeir
[not found] ` <1407260041-19234-1-git-send-email-bpringlemeir-ygJ1pmMJ17cAvxtiuMwx3w@public.gmane.org>
2014-08-06 7:36 ` [PATCH 0/2] vf610-twr device updates Stefan Agner
2014-08-06 9:11 ` Shawn Guo [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=20140806091120.GK2167@dragon \
--to=shawn.guo@freescale.com \
--cc=bpringlemeir@nbsps.com \
--cc=devicetree@vger.kernel.org \
--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).