From: Stephen Warren <swarren@wwwdotorg.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2 0/9] tegra: SPI drivers
Date: Mon, 14 Jan 2013 11:50:23 -0700 [thread overview]
Message-ID: <50F4536F.7030801@wwwdotorg.org> (raw)
In-Reply-To: <1357981631-21245-1-git-send-email-amartin@nvidia.com>
On 01/12/2013 02:07 AM, Allen Martin wrote:
> This series updates the tegra20 SPI driver to add fdt support and adds
> a new tegra30 SPI driver.
Aside from any comments I or anyone has made,
Reviewed-by: Stephen Warren <swarren@nvidia.com>
prev parent reply other threads:[~2013-01-14 18:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-12 9:07 [U-Boot] [PATCH v2 0/9] tegra: SPI drivers Allen Martin
2013-01-12 9:07 ` [U-Boot] [PATCH v2 1/9] tegra: fdt: sort dts files Allen Martin
2013-01-12 16:44 ` Simon Glass
2013-01-12 9:07 ` [U-Boot] [PATCH v2 2/9] tegra: fdt: add apbdma node Allen Martin
2013-01-12 9:07 ` [U-Boot] [PATCH v2 3/9] tegra20: fdt: add SPI SFLASH node Allen Martin
2013-01-14 18:44 ` Stephen Warren
2013-01-12 9:07 ` [U-Boot] [PATCH v2 4/9] tegra: spi: add fdt support to tegra SPI SFLASH driver Allen Martin
2013-01-12 9:07 ` [U-Boot] [PATCH v2 5/9] tegra30: add SBC1 to periph id mapping table Allen Martin
2013-01-12 16:57 ` Simon Glass
2013-01-12 9:07 ` [U-Boot] [PATCH v2 6/9] tegra30: fdt: add SPI SLINK nodes Allen Martin
2013-01-12 17:01 ` Simon Glass
2013-01-12 9:07 ` [U-Boot] [PATCH v2 7/9] tegra: add addresses of SPI SLINK controllers Allen Martin
2013-01-12 16:58 ` Simon Glass
2013-01-12 9:07 ` [U-Boot] [PATCH v2 8/9] tegra: add SPI SLINK driver Allen Martin
2013-01-12 16:56 ` Simon Glass
2013-01-14 18:49 ` Stephen Warren
2013-01-15 4:33 ` Allen Martin
2013-01-15 16:36 ` Stephen Warren
2013-01-22 14:06 ` Simon Glass
2013-01-15 4:27 ` Allen Martin
2013-01-22 13:56 ` Simon Glass
2013-01-12 9:07 ` [U-Boot] [PATCH v2 9/9] tegra: cardhu: config: enable SPI Allen Martin
2013-01-12 16:57 ` Simon Glass
2013-01-14 18:50 ` Stephen Warren [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=50F4536F.7030801@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.