From: Eric Nelson <eric.nelson@boundarydevices.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/3] mxc_spi refactoring (for mx6q and mx6qsabrelite)
Date: Tue, 31 Jan 2012 06:39:44 -0700 [thread overview]
Message-ID: <4F27EF20.9050100@boundarydevices.com> (raw)
In-Reply-To: <CAB4PhKfiTXZf6W4hdDDkpsyXnT7Yw4ibF532f4rzvQYm7MCv-A@mail.gmail.com>
On 01/30/2012 11:51 PM, Jason Liu wrote:
> Eric,
>
> 2012/1/31 Eric Nelson<eric.nelson@boundarydevices.com>:
>> This patch set refactors mxc_spi as described in
>> http://lists.denx.de/pipermail/u-boot/2010-March/068791.html
>> and requested in
>> http://lists.denx.de/pipermail/u-boot/2012-January/116023.html
>> in order to add support for the MX6Q in general and the mx6qsabrelite
>> specifically.
>
> If this patch-set is re-send, please specify version Vx and change-log. Thanks,
>
Hi Jason,
I wasn't quite sure how to handle that, since I split up a 7-patch
series into independent parts.
Any guidance?
next prev parent reply other threads:[~2012-01-31 13:39 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-30 19:52 [U-Boot] [PATCH 0/3] mxc_spi refactoring (for mx6q and mx6qsabrelite) Eric Nelson
2012-01-30 19:52 ` [U-Boot] [PATCH 1/3] mxc_spi: move machine specifics into CPU headers Eric Nelson
2012-01-31 9:15 ` Jason Hui
2012-01-30 19:52 ` [U-Boot] [PATCH 2/3] mx6q: Add support for ECSPI through mxc_spi driver Eric Nelson
2012-01-31 9:20 ` Jason Hui
2012-01-30 19:52 ` [U-Boot] [PATCH 3/3] mx6q: mx6qsabrelite: Add ECSPI support to the Sabrelite platform Eric Nelson
2012-01-31 9:31 ` Jason Hui
2012-01-31 14:16 ` Eric Nelson
2012-01-31 15:00 ` Stefano Babic
2012-01-31 17:50 ` [U-Boot] MX6q SPI refactoring and related patches Eric Nelson
2012-01-31 6:51 ` [U-Boot] [PATCH 0/3] mxc_spi refactoring (for mx6q and mx6qsabrelite) Jason Liu
2012-01-31 6:59 ` Jason Hui
2012-01-31 13:39 ` Eric Nelson [this message]
2012-02-01 4:49 ` Jason Hui
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=4F27EF20.9050100@boundarydevices.com \
--to=eric.nelson@boundarydevices.com \
--cc=u-boot@lists.denx.de \
/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