All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peng Fan <van.freenix@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH V4 1/2] mmc: sd: extracting erase related information from sd status
Date: Thu, 8 Sep 2016 09:51:24 +0800	[thread overview]
Message-ID: <20160908015123.GD9097@linux-7smt.suse> (raw)
In-Reply-To: <489a5e03-15c9-c3f1-106b-28056f843094@samsung.com>

On Thu, Sep 08, 2016 at 10:49:53AM +0900, Jaehoon Chung wrote:
>Hi Peng,
>
>On 09/08/2016 10:42 AM, Peng Fan wrote:
>> Hi Jaehoon,
>> On Wed, Sep 07, 2016 at 03:52:53PM +0900, Jaehoon Chung wrote:
>>> Hi Peng,
>>>
>>> On 09/01/2016 12:13 PM, Peng Fan wrote:
>>>> Add function to read SD_STATUS information.
>>>> According to the information, get erase_timeout/erase_size/erase_offset.
>>>> Add a structure sd_ssr to include the erase related information.
>>>
>>> Sorry for late..I'm testing with your patch on my SD-card.
>>> After that, I will apply yours. Before applied this, i will check more carefully for not doing previous my mistake.
>> 
>> The issue in the previous patch set is that linux/size.h is not included in sandbox.h.
>> In this patchset, I include linux/size.h in mmc.h:)
>
>Right, i have checked the test of building with your patch.
>There is no problem..just i want to run your patch for erasing SD-card. Could you wait for one day?

Yeah. Ok for me :)

Thanks,
Peng.

  reply	other threads:[~2016-09-08  1:51 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20160901031407epcas1p3e0ab48ce0e709a80b65cac28eccdf155@epcas1p3.samsung.com>
2016-09-01  3:13 ` [U-Boot] [PATCH V4 1/2] mmc: sd: extracting erase related information from sd status Peng Fan
2016-09-01  3:13   ` [U-Boot] [PATCH V4 2/2] mmc: sd: optimize erase Peng Fan
2016-09-07  6:52   ` [U-Boot] [PATCH V4 1/2] mmc: sd: extracting erase related information from sd status Jaehoon Chung
2016-09-08  1:42     ` Peng Fan
2016-09-08  1:49       ` Jaehoon Chung
2016-09-08  1:51         ` Peng Fan [this message]
2016-09-08 13:47           ` 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=20160908015123.GD9097@linux-7smt.suse \
    --to=van.freenix@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 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.