From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/3] ARM:dts:vf610-twr:Enable DSPI0 devices and Flash at26df081a
Date: Tue, 9 Jul 2013 11:07:23 +0100 [thread overview]
Message-ID: <20130709100723.GS27646@sirena.org.uk> (raw)
In-Reply-To: <20130709052925.GD16656@S2101-09.ap.freescale.net>
On Tue, Jul 09, 2013 at 01:29:27PM +0800, Shawn Guo wrote:
> On Mon, Jul 08, 2013 at 12:36:01PM +0100, Mark Brown wrote:
> > This should be fine to merge via arm-soc, it's no real dependency on the
> > actual SPI driver.
> It has dependency on the actual SPI driver where the DT bindings are
> defined, so I would only take the patches after the driver parts gets
> accepted.
The bindings are all totally generic ones for a SPI controller, there's
nothing controversial or even device specific about them so I'm happy to
say the bindings are fine as-is.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130709/06099851/attachment.sig>
next prev parent reply other threads:[~2013-07-09 10:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-08 8:37 [PATCH 1/3] spi:Add Freescale DSPI driver for Vybrid VF610 platform Chao Fu
2013-07-08 8:37 ` [PATCH 2/3] ARM:dts: vf610: Add DSPI nodes Chao Fu
2013-07-08 11:35 ` Mark Brown
2013-07-08 8:37 ` [PATCH 3/3] ARM:dts:vf610-twr:Enable DSPI0 devices and Flash at26df081a Chao Fu
2013-07-08 11:36 ` Mark Brown
2013-07-09 5:29 ` Shawn Guo
2013-07-09 10:07 ` Mark Brown [this message]
2013-07-09 12:52 ` Shawn Guo
2013-07-09 14:44 ` Mark Brown
2013-07-09 15:02 ` Shawn Guo
2013-07-09 15:02 ` [PATCH 1/3] spi:Add Freescale DSPI driver for Vybrid VF610 platform Mark Brown
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=20130709100723.GS27646@sirena.org.uk \
--to=broonie@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).