From: per.forlin@linaro.org (Per Forlin)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 0/3] Make fault injection available for MMC IO
Date: Tue, 26 Jul 2011 22:11:56 +0200 [thread overview]
Message-ID: <1311711119-6286-1-git-send-email-per.forlin@linaro.org> (raw)
The first version of this patch is a part of mmc non-blocking v9 patchset:
[PATCH v9 11/12] mmc: core: add random fault injection
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.
Per Forlin (3):
fault-inject: make fault injection available for modules
mmc: core: add random fault injection
fault injection: add documentation on MMC IO fault injection
Documentation/fault-injection/fault-injection.txt | 5 ++
drivers/mmc/core/core.c | 45 +++++++++++++++++++++
drivers/mmc/core/debugfs.c | 26 ++++++++++++
include/linux/mmc/host.h | 7 +++
lib/Kconfig.debug | 11 +++++
lib/fault-inject.c | 2 +
6 files changed, 96 insertions(+), 0 deletions(-)
--
1.7.4.1
next reply other threads:[~2011-07-26 20:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-26 20:11 Per Forlin [this message]
2011-07-26 20:11 ` [PATCH v4 1/3] fault-inject: make fault injection available for modules Per Forlin
2011-07-26 20:11 ` [PATCH v4 2/3] mmc: core: add random fault injection Per Forlin
2011-07-26 23:17 ` Akinobu Mita
2011-07-27 9:02 ` Per Forlin
2011-07-27 16:08 ` Akinobu Mita
2011-07-27 19:46 ` Per Forlin
2011-07-26 20:11 ` [PATCH v4 3/3] fault injection: add documentation on MMC IO " Per Forlin
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=1311711119-6286-1-git-send-email-per.forlin@linaro.org \
--to=per.forlin@linaro.org \
--cc=linux-arm-kernel@lists.infradead.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).