From: Illia Smyrnov <x0194613@ti.com>
To: Mark Brown <broonie@kernel.org>
Cc: Illia Smyrnov <illia.smyrnov@ti.com>,
Grant Likely <grant.likely@linaro.org>,
Rob Herring <rob.herring@calxeda.com>,
Rob Landley <rob@landley.net>, Daniel Mack <zonque@gmail.com>,
Matthias Brugger <matthias.bgg@gmail.com>,
Tony Lindgren <tony@atomide.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
<devicetree-discuss@lists.ozlabs.org>,
<linux-doc@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<spi-devel-general@lists.sourceforge.net>,
<linux-omap@vger.kernel.org>
Subject: Re: [PATCH v3 2/2] spi: omap2-mcspi: Add FIFO buffer support
Date: Mon, 17 Jun 2013 16:39:02 +0300 [thread overview]
Message-ID: <51BF1176.7070608@ti.com> (raw)
In-Reply-To: <20130617091630.GZ1403@sirena.org.uk>
On 06/17/2013 12:16 PM, Mark Brown wrote:
> On Fri, Jun 14, 2013 at 07:12:08PM +0300, Illia Smyrnov wrote:
>> The MCSPI controller has a built-in FIFO buffer to unload the DMA or interrupt
>> handler and improve data throughput. This patch adds FIFO buffer support for SPI
>> transfers in DMA mode.
>
> This looks good but doesn't apply against my topic/omap branch - can you
> please check and resend? Probably something that applies against -next
> will be fine.
>
I fixed it and sent v4 of "spi: omap2-mcspi: Add FIFO buffer support" patch.
prev parent reply other threads:[~2013-06-17 13:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-14 16:12 [PATCH v3 0/2] spi: omap2-mcspi: add FIFO buffer support Illia Smyrnov
[not found] ` <1371226328-24147-1-git-send-email-illia.smyrnov-l0cyMroinI0@public.gmane.org>
2013-06-14 16:12 ` [PATCH v3 1/2] spi: omap2-mcspi: Move bytes per word calculation to the function Illia Smyrnov
2013-06-17 9:14 ` Mark Brown
2013-06-14 16:12 ` [PATCH v3 2/2] spi: omap2-mcspi: Add FIFO buffer support Illia Smyrnov
2013-06-17 9:16 ` Mark Brown
2013-06-17 13:39 ` Illia Smyrnov [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=51BF1176.7070608@ti.com \
--to=x0194613@ti.com \
--cc=broonie@kernel.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=grant.likely@linaro.org \
--cc=gregkh@linuxfoundation.org \
--cc=illia.smyrnov@ti.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=rob.herring@calxeda.com \
--cc=rob@landley.net \
--cc=spi-devel-general@lists.sourceforge.net \
--cc=tony@atomide.com \
--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;
as well as URLs for NNTP newsgroup(s).