From: majianpeng <majianpeng@gmail.com>
To: NeilBrown <neilb@suse.de>, agk <agk@redhat.com>
Cc: linux-raid <linux-raid@vger.kernel.org>, dm-devel <dm-devel@redhat.com>
Subject: [PATCH 0/3] Add a new func to handle with clearing up for stoping dm-raid.
Date: Thu, 15 Nov 2012 16:46:54 +0800 [thread overview]
Message-ID: <201211151646510171304@gmail.com> (raw)
Because dm-raid call md_stop to clear up,but md_stop can't clear up completely.
So add a new func to do.
Jianpeng Ma (3):
md:Add a func 'dm_md_stop' for dm-raid to clear up md resource.
dm: When stoping dm-raid, it call dm_md_stop rather than md_stop to
do clear-up work.
md: Remove EXPORT_SYMBOL_GPL(md_stop).
drivers/md/dm-raid.c | 4 ++--
drivers/md/md.c | 10 +++++++++-
drivers/md/md.h | 1 +
3 files changed, 12 insertions(+), 3 deletions(-)
--
1.7.9.5
root@majianpeng:/mnt/kernel/linux# cat 0000-cover-letter.patch
From f43f22cb5307d5ad8dfe17aa471e3f39d2c9f1dc Mon Sep 17 00:00:00 2001
From: Jianpeng Ma <majianpeng@gmail.com>
Date: Fri, 16 Nov 2012 07:04:56 +0800
Subject: [PATCH 0/3] Add a new func to handle with clearing up for stoping
dm-raid.
Because dm-raid call md_stop to clear up,but md_stop can't clear up completely.
So add a new func to do.
Jianpeng Ma (3):
md:Add a func 'dm_md_stop' for dm-raid to clear up md resource.
dm: When stoping dm-raid, it call dm_md_stop rather than md_stop to
do clear-up work.
md: Remove EXPORT_SYMBOL_GPL(md_stop).
drivers/md/dm-raid.c | 4 ++--
drivers/md/md.c | 10 +++++++++-
drivers/md/md.h | 1 +
3 files changed, 12 insertions(+), 3 deletions(-)
--
1.7.9.5
next reply other threads:[~2012-11-15 8:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-15 8:46 majianpeng [this message]
2012-11-18 23:49 ` [PATCH 0/3] Add a new func to handle with clearing up for stoping dm-raid NeilBrown
2012-11-19 0:36 ` majianpeng
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=201211151646510171304@gmail.com \
--to=majianpeng@gmail.com \
--cc=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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).