public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 0/7] omap mmc: implement card detect and write protection
Date: Sat, 9 Mar 2013 07:18:44 -0500	[thread overview]
Message-ID: <513B28A4.4010901@ti.com> (raw)
In-Reply-To: <513AE090.5030108@compulab.co.il>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 03/09/2013 02:11 AM, Igor Grinberg wrote:
> Hi guys,
> 
> This patch set is "floating" already for _three_ months. All
> comments were addressed, it introduces negative diff stat, and
> provides two useful features (also for production automation).
> 
> Andy hasn't been responding for quite a while. I think this patch
> set is good enough for merging. There is no reason for it to float
> any longer.
> 
> Please, merge it either via Tom's tree or anyone else's staging.

I grabbed this locally yesterday and the only issue is that there's
new boards that need their mmc calls updated.  I should have this
merged soon.

- -- 
Tom
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iQIcBAEBAgAGBQJROyikAAoJENk4IS6UOR1WSC8P/2SNB6v96Cmbw+hwpNl3iJSa
stk2r7pxOUBvMJR7ZMzjVz53DUn8OvKbc+0eaPR12VwHGY/i9GuOqHfcu31dx1q5
Hq4W5J+MS97czVK/6S5FcbDLFr8araBHM8AZwQNz1DqQVoswLA6bHKepNdzXzp+q
X04K0dNP4TbikazytLiStLiGcS58VORVKIrT7coWjapIOO9+bcKhCq4XgsuGOluy
YGIbn0s3kewoDxCbdpDQIu5QBpbNv13wTYWqRFVlaf5x+sBvUxtSTPPHNjl8I6c8
O3acMI+5AGpsNyQrRqRCbpZ3ce9NZw2/7ORS0GOLyWF/TAH0qv7+W8OuK8L+YtHm
8ivqSypSA33A0dneC0U3wu72lkBRWmA8tXjWifyNh0bKfL+5eKo37ZT3RL2sCmsl
n8aNXIwnMHEOXt+g9afU4g0EgD4EfJY3CF0sJcB8VuxDttkFYs/nVIwNRdg0Ivq3
xHEdPrgbBZsBbpbpjaxX6gatz8zdBl77ky4roCc9OQ5xJpQmO7lab5wAJK8Un5vl
ywGZa5akE7IHTrgpOlDKANe8PUsfSR8YnRkzov2rUuoXnxiT/avtWQuQXch2nmbR
Als1LbNapRwevslrGFUpcbQwOefXOIlaX+ise6Jelky44/udoxCPFxkPPjXgqSRU
Kw9IGLWgup5EylWGHitM
=JIxn
-----END PGP SIGNATURE-----

      reply	other threads:[~2013-03-09 12:18 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-03 12:19 [U-Boot] [PATCH 0/7] omap mmc: implement card detect and write protection Nikita Kiryanov
2012-12-03 12:19 ` [U-Boot] [PATCH 1/7] omap: consolidate common mmc definitions Nikita Kiryanov
2012-12-03 12:19 ` [U-Boot] [PATCH 2/7] omap_hsmmc: fix out of bounds array access Nikita Kiryanov
2012-12-03 12:19 ` [U-Boot] [PATCH 3/7] omap_hsmmc: introduce omap_hsmmc_data struct Nikita Kiryanov
2012-12-03 12:19 ` [U-Boot] [PATCH 4/7] omap_hsmmc: implement driver check for card detection Nikita Kiryanov
2012-12-18 23:52   ` Tom Rini
2012-12-19  6:58     ` Nikita Kiryanov
2012-12-03 12:19 ` [U-Boot] [PATCH 5/7] cm-t35: implement board specific card detect check Nikita Kiryanov
2012-12-03 12:19 ` [U-Boot] [PATCH 6/7] mmc: add support for write protection Nikita Kiryanov
2012-12-03 12:19 ` [U-Boot] [PATCH 7/7] omap_hsmmc: add driver check " Nikita Kiryanov
2013-02-15 21:22   ` Tom Rini
2012-12-18  7:58 ` [U-Boot] [PATCH 0/7] omap mmc: implement card detect and " Nikita Kiryanov
2012-12-30  6:13 ` Nikita Kiryanov
2013-01-07 14:43   ` Tom Rini
2013-01-31  7:44     ` Igor Grinberg
2013-02-13  7:27 ` Nikita Kiryanov
2013-02-15 21:24 ` Tom Rini
2013-03-05  7:53   ` Nikita Kiryanov
2013-03-09  7:11 ` Igor Grinberg
2013-03-09 12:18   ` Tom Rini [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=513B28A4.4010901@ti.com \
    --to=trini@ti.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