From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Matthias Brugger <matthias.bgg@gmail.com>
Cc: Grant Likely <grant.likely@secretlab.ca>,
Rob Herring <rob.herring@calxeda.com>,
Rob Landley <rob@landley.net>, Daniel Mack <zonque@gmail.com>,
Enric Balletbo Serra <eballetbo@gmail.com>,
Javier Martinez Canillas <martinez.javier@gmail.com>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
linux-doc@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
spi-devel-general@lists.sourceforge.net,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
ezequiel.garcia@free-electrons.com
Subject: Re: [PATCH] spi: spi-omap2-mcspi.c: Add dts for slave device configuration.
Date: Mon, 8 Apr 2013 13:40:36 +0100 [thread overview]
Message-ID: <20130408124036.GI9243@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CABuKBeKN+cPbsf95mTvDfzAwzOh4V-+bycp=sujNndDeMG2HMw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 421 bytes --]
On Mon, Apr 08, 2013 at 02:18:00PM +0200, Matthias Brugger wrote:
> 2013/3/26 Matthias Brugger <matthias.bgg@gmail.com>
> > TI omap2 mcspi allows the slave devices to configure the behavior of
> > the SPI master. This patch adds device tree support to the existing
> > options.
> Any comments on this patch?
Don't send contentless pings, and it appears to have only been a couple
of weeks since it was first posted...
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-04-08 12:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-25 23:00 [PATCH] spi: spi-omap2-mcspi.c: Add dts for slave device configuration Matthias Brugger
[not found] ` <CABuKBeKN+cPbsf95mTvDfzAwzOh4V-+bycp=sujNndDeMG2HMw@mail.gmail.com>
2013-04-08 12:40 ` Mark Brown [this message]
2013-04-17 15:11 ` Mark Brown
[not found] ` <CAB=otbTtRN9xyO0whNz-UbW+Xo0_X8XWLcWZt=7MfUfrnNqwww@mail.gmail.com>
2013-05-14 9:53 ` Illia Smyrnov
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=20130408124036.GI9243@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=eballetbo@gmail.com \
--cc=ezequiel.garcia@free-electrons.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=martinez.javier@gmail.com \
--cc=matthias.bgg@gmail.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=zonque@gmail.com \
/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