From: broonie@kernel.org (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] spi: sirf: add support for USP-based SPI
Date: Tue, 19 May 2015 12:22:01 +0100 [thread overview]
Message-ID: <20150519112201.GH2761@sirena.org.uk> (raw)
In-Reply-To: <1431602829-12428-1-git-send-email-21cnbao@gmail.com>
On Thu, May 14, 2015 at 11:27:09AM +0000, Barry Song wrote:
> From: Qipan Li <Qipan.Li@csr.com>
>
> USP is a general purpose serial port in SiRFSoC, which can work as SPI.
> the most data flow of USP and pure SPI is same with main differences
> in registers layout.
This doesn't apply against current code, please check and resend.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 473 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150519/59ae7e47/attachment.sig>
next prev parent reply other threads:[~2015-05-19 11:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-14 11:27 [PATCH v2] spi: sirf: add support for USP-based SPI Barry Song
2015-05-19 11:22 ` Mark Brown [this message]
2015-05-19 14:41 ` Barry Song
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=20150519112201.GH2761@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;
as well as URLs for NNTP newsgroup(s).