From: merez@codeaurora.org
To: Chris Ball <cjb@laptop.org>
Cc: "Luca Porzio (lporzio)" <lporzio@micron.com>,
Yaniv Gardi <ygardi@codeaurora.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"vgoyal@redhat.com" <vgoyal@redhat.com>,
"tj@kernel.org" <tj@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH v1] mmc: card: Adding support for sanitize in eMMC 4.5
Date: Mon, 15 Apr 2013 01:08:10 -0700 [thread overview]
Message-ID: <8c0a691851491a66c7df58b9a2ca89ec.squirrel@www.codeaurora.org> (raw)
In-Reply-To: <877gkipebd.fsf@octavius.laptop.org>
Hi Chris and Luca,
Sorry for the late response.
Yaniv is on vacation for the last month and will be back at the end of the
week.
We will add the HPI in case Sanitize times-out.
Thanks,
Maya
> Hi Yaniv, Maya,
>
> On Mon, Mar 11 2013, Luca Porzio (lporzio) wrote:
>> In case of Sanitize timeout, the eMMC might go in an unclear state.
>> May I suggest to:
>> - issue an HPI before leaving thus bring the eMMC back into safe status
>> - report the 'sanitize not complete error' and let the user decide on
>> Whether he wants to re-issue (i.e. continue) the sanitize or just let
>> it go.
>
> Can you respond to this review feedback from Luca, please?
>
> Thanks,
>
> - Chris.
> --
> Chris Ball <cjb@laptop.org> <http://printf.net/>
> One Laptop Per Child
> --
> 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
>
--
Maya Erez
QUALCOMM ISRAEL, on behalf of Qualcomm Innovation Center, Inc. is a member
of Code Aurora Forum, hosted by The Linux Foundation
prev parent reply other threads:[~2013-04-15 8:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-24 11:38 [PATCH v1] mmc: card: Adding support for sanitize in eMMC 4.5 Yaniv Gardi
2013-03-11 18:36 ` Luca Porzio (lporzio)
2013-03-21 19:49 ` merez
2013-03-25 13:17 ` Luca Porzio (lporzio)
2013-04-04 14:20 ` Chris Ball
2013-04-15 8:08 ` merez [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=8c0a691851491a66c7df58b9a2ca89ec.squirrel@www.codeaurora.org \
--to=merez@codeaurora.org \
--cc=cjb@laptop.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=lporzio@micron.com \
--cc=tj@kernel.org \
--cc=vgoyal@redhat.com \
--cc=ygardi@codeaurora.org \
/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