From: Chris Ball <cjb@laptop.org>
To: Yaniv Gardi <ygardi@codeaurora.org>
Cc: linux-mmc@vger.kernel.org, linux-arm-msm@vger.kernel.org,
'open list' <linux-kernel@vger.kernel.org>,
merez@codeaurora.org,
Girish K S <girish.shivananjappa@linaro.org>,
"S, Venkatraman" <svenkatr@ti.com>,
"Dong, Chuanxiao" <chuanxiao.dong@intel.com>,
Stephen Boyd <sboyd@codeaurora.org>,
Jaehoon Chung <jh80.chung@samsung.com>,
Kyungmin Park <kmpark@infradead.org>
Subject: Re: [PATCH RESEND v7 2/2] mmc: card: Adding support for sanitize in eMMC 4.5
Date: Tue, 24 Jul 2012 02:56:17 -0400 [thread overview]
Message-ID: <87obn5y7e6.fsf_-_@octavius.laptop.org> (raw)
In-Reply-To: <000001cd6967$2ce2a010$86a7e030$@codeaurora.org> (Yaniv Gardi's message of "Tue, 24 Jul 2012 09:40:08 +0300")
Hi Yaniv,
On Tue, Jul 24 2012, Yaniv Gardi wrote:
> Are there any additional open issues to discuss regarding the sanitize
> capability ?
> If not, we would like to see this patch pushed into mmc-next.
I think you've responded to all of the open issues, thanks -- I'm adding
everyone who made a review comment to the CC list for this mail, so that
they can check whether v7 addresses their concerns, and consider asking
more questions or providing a Reviewed-by.
How are you doing with getting the block layer patches merged? I'd like
to get both layers into linux-next around the same time, if we can.
I wonder if there's any way to test whether sanitize has had an effect.
It would be good to know whether it actually does anything on a specific
eMMC, although I'm sure it's difficult to tell.
Thanks!
- Chris.
--
Chris Ball <cjb@laptop.org> <http://printf.net/>
One Laptop Per Child
next prev parent reply other threads:[~2012-07-24 6:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-28 8:32 [PATCH RESEND v7 0/2] *** adding and exposing SANITIZE capability to the user space via a unique IOCTL *** Yaniv Gardi
2012-06-28 8:32 ` [PATCH RESEND v7 1/2] block: ioctl support for sanitize in eMMC 4.5 Yaniv Gardi
2012-06-28 8:41 ` merez
2012-07-17 10:48 ` Yaniv Gardi
2012-07-09 8:37 ` Girish K S
2012-07-09 9:03 ` Girish K S
2012-07-09 10:02 ` Girish K S
2013-01-21 8:04 ` Maya Erez
2012-06-28 8:32 ` [PATCH RESEND v7 2/2] mmc: card: Adding " Yaniv Gardi
2012-06-28 8:43 ` merez
2012-07-17 10:51 ` Yaniv Gardi
2012-07-19 6:46 ` Chris Ball
2012-07-19 11:25 ` merez
2012-07-24 6:40 ` Yaniv Gardi
2012-07-24 6:56 ` Chris Ball [this message]
2012-07-25 9:39 ` Yaniv Gardi
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=87obn5y7e6.fsf_-_@octavius.laptop.org \
--to=cjb@laptop.org \
--cc=chuanxiao.dong@intel.com \
--cc=girish.shivananjappa@linaro.org \
--cc=jh80.chung@samsung.com \
--cc=kmpark@infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=merez@codeaurora.org \
--cc=sboyd@codeaurora.org \
--cc=svenkatr@ti.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;
as well as URLs for NNTP newsgroup(s).