From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH RESEND 0/2] spi: sun4i: add DMA support
Date: Fri, 26 Feb 2016 21:15:42 +0900 [thread overview]
Message-ID: <20160226121542.GP18327@sirena.org.uk> (raw)
In-Reply-To: <1456466217-6793-1-git-send-email-plaes@plaes.org>
On Fri, Feb 26, 2016 at 07:56:55AM +0200, Priit Laes wrote:
> While trying to get SPI TFT screen working with Cubietruck, I noticed that
> at current state driver didn't actually support SPI data bursts bigger than
> n bytes (n is probably ~64 bytes).
If you're going to add noise like "RESEND" to your subject lines (which
makes the visible space for the actual subject smaller so makes handling
incoming mail harder) please at least make sure it's true, you've not
sent these before.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160226/681c8e01/attachment.sig>
prev parent reply other threads:[~2016-02-26 12:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-26 5:56 [PATCH RESEND 0/2] spi: sun4i: add DMA support Priit Laes
2016-02-26 5:56 ` [PATCH 1/2] " Priit Laes
2016-02-26 12:25 ` Mark Brown
2016-02-26 12:51 ` Michal Suchanek
2016-03-06 21:42 ` Maxime Ripard
2016-03-10 9:01 ` Michal Suchanek
2016-03-17 7:27 ` Maxime Ripard
2016-03-17 10:58 ` Michal Suchanek
2016-03-17 11:43 ` Mark Brown
2016-03-17 11:54 ` Michal Suchanek
2016-03-17 11:58 ` Mark Brown
2016-03-18 20:23 ` Maxime Ripard
2016-03-18 20:33 ` Mark Brown
2016-02-26 5:56 ` [PATCH 2/2] ARM: sunxi: spi: add notice about SPI FIFO limit Priit Laes
2016-03-06 18:12 ` Maxime Ripard
2016-02-26 12:15 ` Mark Brown [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=20160226121542.GP18327@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