From: "Yaniv Gardi" <ygardi@codeaurora.org>
To: 'Chris Ball' <cjb@laptop.org>, axboe@kernel.dk
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>merez@codeaurora.org
Subject: RE: [PATCH RESEND v7 2/2] mmc: card: Adding support for sanitize in eMMC 4.5
Date: Wed, 25 Jul 2012 12:39:43 +0300 [thread overview]
Message-ID: <000401cd6a49$6e74aef0$4b5e0cd0$@codeaurora.org> (raw)
In-Reply-To: <87obn5y7e6.fsf_-_@octavius.laptop.org>
+ Jens Axboe
Hi Jens,
Can you please review the v8 patch and refer to it? As seen below,
everything is all set to push the change in the mmc layer,
But it's better to push the feature to both modules
Hi Chris,
I just uploaded a v8, which has small fix in the block layer. It has no
changes at all, in the mmc layer.
Hope we soon have a reply from Jens regarding when the sanitize patch can be
pushed in to linux-next in the block layer.
Thanks,
Yaniv
= > -----Original Message-----
= > From: linux-mmc-owner@vger.kernel.org [mailto:linux-mmc-
= > owner@vger.kernel.org] On Behalf Of Chris Ball
= > Sent: Tuesday, July 24, 2012 9:56 AM
= > To: Yaniv Gardi
= > Cc: linux-mmc@vger.kernel.org; linux-arm-msm@vger.kernel.org; 'open
= > list'; merez@codeaurora.org; Girish K S; S, Venkatraman; Dong,
Chuanxiao;
= > Stephen Boyd; Jaehoon Chung; Kyungmin Park
= > Subject: Re: [PATCH RESEND v7 2/2] mmc: card: Adding support for
= > sanitize in eMMC 4.5
= >
= > 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
= > --
= > 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
prev parent reply other threads:[~2012-07-25 9:39 UTC|newest]
Thread overview: 15+ 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
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
2012-07-25 9:39 ` Yaniv Gardi [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='000401cd6a49$6e74aef0$4b5e0cd0$@codeaurora.org' \
--to=ygardi@codeaurora.org \
--cc=axboe@kernel.dk \
--cc=chuanxiao.dong@intel.com \
--cc=cjb@laptop.org \
--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 \
/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).