From: Laxman Dewangan <ldewangan@nvidia.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Manish Badarkhe <badarkhe.manish@gmail.com>,
"rob.herring@calxeda.com" <rob.herring@calxeda.com>,
"broonie@opensource.wolfsonmicro.com"
<broonie@opensource.wolfsonmicro.com>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
"devicetree-discuss@lists.ozlabs.org"
<devicetree-discuss@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"spi-devel-general@lists.sourceforge.net"
<spi-devel-general@lists.sourceforge.net>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
Stephen Warren <swarren@nvidia.com>
Subject: Re: [PATCH V3] spi: tegra114: add spi driver
Date: Thu, 28 Mar 2013 17:08:45 +0530 [thread overview]
Message-ID: <51542BC5.10701@nvidia.com> (raw)
In-Reply-To: <20130302230906.141BE3E336A@localhost>
On Sunday 03 March 2013 04:39 AM, Grant Likely wrote:
> On Fri, 22 Feb 2013 19:59:11 +0530, Manish Badarkhe <badarkhe.manish@gmail.com> wrote:
>> On Fri, Feb 22, 2013 at 6:07 PM, Laxman Dewangan <ldewangan@nvidia.com> wrote:
>>> Add SPI driver for NVIDIA's Tegra114 SPI controller. This controller
>>> is different than the older SoCs SPI controller in internal design as
>>> well as register interface.
>>>
>>> This driver supports the:
>>> - non DMA based transfer for smaller transfer i.e. less than FIFO depth.
>>> - APB DMA based transfer for lager transfer i.e. more than FIFO depth.
>> s/lager/larger
> Applied, thanks. And I fixed up the typo when I did.
>
Grant,
I still do not see this change in linux-next? Are you going to put this
change for K3.10? Wanted to close some of stuff from Tegra side.
prev parent reply other threads:[~2013-03-28 11:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-22 12:37 [PATCH V3] spi: tegra114: add spi driver Laxman Dewangan
2013-02-22 14:29 ` Manish Badarkhe
2013-02-22 18:02 ` Mark Brown
2013-03-03 12:49 ` Manish Badarkhe
2013-03-02 23:09 ` Grant Likely
2013-03-28 11:38 ` Laxman Dewangan [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=51542BC5.10701@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=badarkhe.manish@gmail.com \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@secretlab.ca \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=rob.herring@calxeda.com \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=swarren@nvidia.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