From: shawnguo@kernel.org (Shawn Guo)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: dts: vfxxx: Include support for dspi[23] functionality.
Date: Tue, 24 Nov 2015 17:49:32 +0800 [thread overview]
Message-ID: <20151124094932.GX11999@tiger> (raw)
In-Reply-To: <1447905280-5172-2-git-send-email-cory.tusar@pid1solutions.com>
On Wed, Nov 18, 2015 at 10:54:40PM -0500, Cory Tusar wrote:
> Extend the existing Vybrid DSPI devicetree implementation to also
> describe the dspi2 and dspi3 functional blocks.
>
> Signed-off-by: Cory Tusar <cory.tusar@pid1solutions.com>
Applied, thanks.
WARNING: multiple messages have this Message-ID (diff)
From: Shawn Guo <shawnguo@kernel.org>
To: Cory Tusar <cory.tusar@pid1solutions.com>
Cc: kernel@pengutronix.de, stefan@agner.ch, robh+dt@kernel.org,
pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
linux@arm.linux.org.uk, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
andrew@lunn.ch, Chris.Healy@zii.aero, Keith.Vennel@zii.aero
Subject: Re: [PATCH] ARM: dts: vfxxx: Include support for dspi[23] functionality.
Date: Tue, 24 Nov 2015 17:49:32 +0800 [thread overview]
Message-ID: <20151124094932.GX11999@tiger> (raw)
In-Reply-To: <1447905280-5172-2-git-send-email-cory.tusar@pid1solutions.com>
On Wed, Nov 18, 2015 at 10:54:40PM -0500, Cory Tusar wrote:
> Extend the existing Vybrid DSPI devicetree implementation to also
> describe the dspi2 and dspi3 functional blocks.
>
> Signed-off-by: Cory Tusar <cory.tusar@pid1solutions.com>
Applied, thanks.
next prev parent reply other threads:[~2015-11-24 9:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 3:54 [PATCH] ARM: dts: vfxxx: Include support for dspi[23] functionality Cory Tusar
2015-11-19 3:54 ` Cory Tusar
2015-11-19 6:41 ` Stefan Agner
2015-11-19 6:41 ` Stefan Agner
2015-11-19 6:41 ` Stefan Agner
2015-11-24 9:49 ` Shawn Guo [this message]
2015-11-24 9:49 ` Shawn Guo
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=20151124094932.GX11999@tiger \
--to=shawnguo@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.