All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jaehoon Chung <jh80.chung@samsung.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] mmc: rpmb: update size format for write_counter
Date: Thu, 29 Jun 2017 18:43:38 +0900	[thread overview]
Message-ID: <243227cf-b4cd-5987-099f-ba20495b99ac@samsung.com> (raw)
In-Reply-To: <1496884804-5731-2-git-send-email-kever.yang@rock-chips.com>

On 06/08/2017 10:20 AM, Kever Yang wrote:
> According to MMC spec, the write_counter is 4-byte length,
> use 'int' instead of 'long' type for the 'long' is not 4-byte
> in 64 bit CPU.
> 
> Signed-off-by: Jason Zhu <jason.zhu@rock-chips.com>
> Signed-off-by: Kever Yang <kever.yang@rock-chips.com>

Applied to u-boot-mmc. Thanks!

Best Regards,
Jaehoon Chung


> ---
> 
>  drivers/mmc/rpmb.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/mmc/rpmb.c b/drivers/mmc/rpmb.c
> index 1c6888f..0b6b622 100644
> --- a/drivers/mmc/rpmb.c
> +++ b/drivers/mmc/rpmb.c
> @@ -67,7 +67,7 @@ struct s_rpmb {
>  	unsigned char mac[RPMB_SZ_MAC];
>  	unsigned char data[RPMB_SZ_DATA];
>  	unsigned char nonce[RPMB_SZ_NONCE];
> -	unsigned long write_counter;
> +	unsigned int write_counter;
>  	unsigned short address;
>  	unsigned short block_count;
>  	unsigned short result;
> 

  parent reply	other threads:[~2017-06-29  9:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20170608012015epcas4p2821661342a6e314e29afcb2390ee7ca2@epcas4p2.samsung.com>
2017-06-08  1:20 ` [U-Boot] [PATCH 1/2] mmc: use new hwpart API when CONFIG_BLK enabled Kever Yang
2017-06-08  1:20   ` [U-Boot] [PATCH 2/2] mmc: rpmb: update size format for write_counter Kever Yang
2017-06-09 12:28     ` Simon Glass
2017-06-13  2:11       ` Kever Yang
2017-06-17  3:40         ` Simon Glass
2017-06-19  6:42         ` Lothar Waßmann
2017-06-29  9:43     ` Jaehoon Chung [this message]
2017-06-09 12:28   ` [U-Boot] [PATCH 1/2] mmc: use new hwpart API when CONFIG_BLK enabled Simon Glass
2017-06-29  9:43   ` Jaehoon Chung

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=243227cf-b4cd-5987-099f-ba20495b99ac@samsung.com \
    --to=jh80.chung@samsung.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 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.