public inbox for linux-mmc@vger.kernel.org
 help / color / mirror / Atom feed
From: "Subhash Jadavani" <subhashj@codeaurora.org>
To: 'Philip Rakity' <prakity@marvell.com>, 'Chris Ball' <cjb@laptop.org>
Cc: linux-mmc@vger.kernel.org, 'Arindam Nath' <arindam.nath@amd.com>
Subject: RE: SD Patches
Date: Wed, 27 Apr 2011 19:13:22 -0700	[thread overview]
Message-ID: <000301cc0549$d9dbbd70$8d933850$@org> (raw)
In-Reply-To: <D25F80F1-828E-40C1-B60A-207EEE2DA4E2@marvell.com>

I have also reviewed Arindam's SD3.0 patches and looks good to me. Although
I haven't tested those yet.

Regards,
Subhash

> -----Original Message-----
> From: linux-mmc-owner@vger.kernel.org [mailto:linux-mmc-
> owner@vger.kernel.org] On Behalf Of Philip Rakity
> Sent: Tuesday, April 26, 2011 7:51 PM
> To: Chris Ball
> Cc: linux-mmc@vger.kernel.org; Arindam Nath
> Subject: SD Patches
> 
> 
> Chris,
> 
> It is important that the patches are put into the linux code for
> testing.
> 
> I have tested and reviewed the code but NOT extensively.
> 
> It works for me doing eMMC (DDR)  and SDIO (SDR50).
> 
> I certainly have no issue with saying I have reviewed the code and
> tested it -- but again only in the areas I am looking at.
> 
> With this provision feel free to add
> 
> Reviewed and Tested-by to the code so we can move forward with its
> integration into mmc-next.
> 
> Philip
> 
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html


  reply	other threads:[~2011-04-28  2:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-27  2:50 SD Patches Philip Rakity
2011-04-28  2:13 ` Subhash Jadavani [this message]
2011-04-28  8:31   ` Wolfram Sang

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='000301cc0549$d9dbbd70$8d933850$@org' \
    --to=subhashj@codeaurora.org \
    --cc=arindam.nath@amd.com \
    --cc=cjb@laptop.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=prakity@marvell.com \
    /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