From: Per Forlin <per.forlin@linaro.org>
To: Akinobu Mita <akinobu.mita@gmail.com>,
akpm@linux-foundation.org,
Linus Walleij <linus.ml.walleij@gmail.com>,
linux-kernel@vger.kernel.org, Randy Dunlap <rdunlap@xenotime.net>,
Chris Ball <cjb@laptop.org>
Cc: linux-doc@vger.kernel.org, linux-mmc@vger.kernel.org,
linaro-dev@lists.linaro.org, linux-mm@kvack.org,
Per Forlin <per.forlin@linaro.org>
Subject: [PATCH --mmotm v8 0/3] Make fault injection available for MMC IO
Date: Tue, 9 Aug 2011 14:07:48 +0200 [thread overview]
Message-ID: <1312891671-28680-1-git-send-email-per.forlin@linaro.org> (raw)
change log:
v2 - Resolve build issue in mmc core.c due to multiple init_module by
removing the fault inject module.
- Export fault injection functions to make them available for modules
- Update fault injection documentation on MMC IO
v3 - add function descriptions in core.c
- use export GPL for fault injection functions
v4 - make the fault_attr per host. This prepares for upcoming patch from
Akinobu that adds support for creating debugfs entries in
arbitrary directory.
v5 - Make use of fault_create_debugfs_attr() in Akinobu's
patch "fault-injection: add ability to export fault_attr in...".
v6 - Fix typo in commit message in patch "export fault injection functions"
v7 - Don't compile in boot param setup function if mmc-core is
built as module.
v8 - Update fault injection documentation.
Add fail_mmc_request to boot option section.
Per Forlin (3):
fault-inject: export fault injection functions
mmc: core: add random fault injection
fault injection: add documentation on MMC IO fault injection
Documentation/fault-injection/fault-injection.txt | 8 +++-
drivers/mmc/core/core.c | 44 +++++++++++++++++++++
drivers/mmc/core/debugfs.c | 27 +++++++++++++
include/linux/mmc/host.h | 7 +++
lib/Kconfig.debug | 11 +++++
lib/fault-inject.c | 2 +
6 files changed, 98 insertions(+), 1 deletions(-)
--
1.7.4.1
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next reply other threads:[~2011-08-09 12:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-09 12:07 Per Forlin [this message]
2011-08-09 12:07 ` [PATCH --mmotm v8 1/3] fault-inject: export fault injection functions Per Forlin
2011-08-09 12:07 ` [PATCH --mmotm v8 2/3] mmc: core: add random fault injection Per Forlin
2011-08-19 11:40 ` Linus Walleij
2011-08-19 12:13 ` Per Forlin
2011-08-09 12:07 ` [PATCH --mmotm v8 3/3] fault injection: add documentation on MMC IO " Per Forlin
2011-08-19 9:53 ` [PATCH --mmotm v8 0/3] Make fault injection available for MMC IO Per Forlin
2011-08-19 17:24 ` Chris Ball
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=1312891671-28680-1-git-send-email-per.forlin@linaro.org \
--to=per.forlin@linaro.org \
--cc=akinobu.mita@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cjb@laptop.org \
--cc=linaro-dev@lists.linaro.org \
--cc=linus.ml.walleij@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-mmc@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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).