From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Maxime Ripard <maxime.ripard@free-electrons.com>
Cc: Grant Likely <grant.likely@secretlab.ca>,
spi-devel-general@lists.sourceforge.net,
Shawn Guo <shawn.guo@linaro.org>,
linux-arm-kernel@lists.infradead.org,
Brian Lilly <brian@crystalfontz.com>
Subject: Re: [PATCH 1/3] spi: spidev: Add device tree bindings
Date: Thu, 1 Nov 2012 14:55:27 +0000 [thread overview]
Message-ID: <20121101145527.GR4413@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1351679410-11026-2-git-send-email-maxime.ripard@free-electrons.com>
[-- Attachment #1.1: Type: text/plain, Size: 196 bytes --]
On Wed, Oct 31, 2012 at 11:30:08AM +0100, Maxime Ripard wrote:
> This will allow to probe spidev from device tree by adding the
> compatible string of each device to this array.
Applied, thanks.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 176 bytes --]
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2012-11-01 14:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-31 10:30 [PATCHv2 0/3] Add spidev to the CFA-10049 Maxime Ripard
[not found] ` <1351679410-11026-1-git-send-email-maxime.ripard-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2012-10-31 10:30 ` [PATCH 1/3] spi: spidev: Add device tree bindings Maxime Ripard
2012-11-01 14:55 ` Mark Brown [this message]
2012-10-31 10:30 ` [PATCH 2/3] spi: spidev: Add Rohm DH2228FV DAC compatible string Maxime Ripard
2012-11-01 14:56 ` Mark Brown
2012-10-31 10:30 ` [PATCH 3/3] ARM: dts: cfa10049: Add the DH2228FV DAC to the DTS Maxime Ripard
2012-11-02 1:56 ` 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=20121101145527.GR4413@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=brian@crystalfontz.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=maxime.ripard@free-electrons.com \
--cc=shawn.guo@linaro.org \
--cc=spi-devel-general@lists.sourceforge.net \
/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).