From: Yaniv Gardi <ygardi@codeaurora.org>
To: linux-mmc@vger.kernel.org
Cc: ygardi@codeaurora.org, merez@codeaurora.org
Subject: [PATCH v6 0/2] *** adding and exposing SANITIZE capability to the user space via a unique IOCTL ***
Date: Thu, 7 Jun 2012 17:17:19 +0300 [thread overview]
Message-ID: <1339078641-20848-1-git-send-email-ygardi@codeaurora.org> (raw)
*** adding and exposing SANITIZE capability to the user space via a unique IOCTL ***
changes patch v5:
added BUG_ON() where needed
changes patch v4:
removed a few debug printouts
changes patch v3:
split the patch into 2 commits - block and mmc/card
added capability MMC_CAP2_SANITIZE to mmc controller
Yaniv Gardi (2):
block: ioctl support for sanitize in eMMC 4.5
mmc: card: Adding support for sanitize in eMMC 4.5
block/blk-core.c | 18 +++++++++--
block/blk-lib.c | 51 +++++++++++++++++++++++++++++++
block/blk-merge.c | 6 ++++
block/elevator.c | 41 ++++++++++++++++++++++++-
block/ioctl.c | 9 +++++
drivers/mmc/card/block.c | 72 ++++++++++++++++++++++++++++++++------------
drivers/mmc/card/queue.c | 10 +++++-
include/linux/blk_types.h | 5 ++-
include/linux/blkdev.h | 3 ++
include/linux/fs.h | 1 +
include/linux/mmc/host.h | 1 +
kernel/trace/blktrace.c | 2 +
12 files changed, 191 insertions(+), 28 deletions(-)
--
1.7.6
--
Sent by a consultant of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum
next reply other threads:[~2012-06-07 14:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-07 14:17 Yaniv Gardi [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-06-07 14:38 [PATCH v6 0/2] *** adding and exposing SANITIZE capability to the user space via a unique IOCTL *** Yaniv Gardi
2012-06-08 11:29 ` S, Venkatraman
2012-06-10 13:49 ` Yaniv Gardi
2012-06-11 3:03 ` Dong, Chuanxiao
2012-06-12 16:19 ` Yaniv Gardi
2012-06-13 20:43 ` S, Venkatraman
2012-06-14 3:22 ` Dong, Chuanxiao
2012-06-11 14:55 ` S, Venkatraman
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=1339078641-20848-1-git-send-email-ygardi@codeaurora.org \
--to=ygardi@codeaurora.org \
--cc=linux-mmc@vger.kernel.org \
--cc=merez@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).