public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Rommel Custodio <sessyargc@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] mmc: support the correct card version for eMMC
Date: Sat, 2 Feb 2013 07:03:53 +0900	[thread overview]
Message-ID: <20130201220353.GA80393@crg> (raw)
In-Reply-To: <510A5BCF.7050407@samsung.com>

Dear Jaehoon,

On 2013.01/31, Jaehoon Chung wrote:
> Hi Rommel,
> 
> Could you review or test for this?

> > eMMC vesrion is supported up to v4.5.
> > But bootloader isn't saw the exact eMMC version.
> > After applied this patch,
> > if use the mmcinfo command, then can see the exactly mmc version.
> > 
> > Signed-off-by: Jaehoon Chung <jh80.chung@samsung.com>
> > Signed-off-by: Kyungmin Park <kyungmin.park@samsung.com>
> > ---
> >  common/cmd_mmc.c  |    2 +-
> >  drivers/mmc/mmc.c |   18 ++++++++++++++++++
> >  include/mmc.h     |   21 +++++++++++++--------
> >  3 files changed, 32 insertions(+), 9 deletions(-)

Doesn't git am cleanly when "mmc: check the revision for sd3.0" is
applied first. And "mmc: check the revision for sd3.0" doesn't git am
cleanly if this patch is applied first. Maybe merging the two patches is
better to avoid this chicken and egg problem.

Builds OK all by itself.

Acked-by: Rommel Custodio <sessyargc@gmail.com>

All the best,
Rommel

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 487 bytes
Desc: not available
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20130202/970c5c7c/attachment.pgp>

  reply	other threads:[~2013-02-01 22:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-30  5:31 [U-Boot] [PATCH] mmc: support the correct card version for eMMC Jaehoon Chung
2013-01-31 11:55 ` Jaehoon Chung
2013-02-01 22:03   ` Rommel Custodio [this message]
2013-04-17 15:37 ` [U-Boot] " Tom Rini

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=20130201220353.GA80393@crg \
    --to=sessyargc@gmail.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