From: Neil Brown <neilb@cse.unsw.edu.au>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: linux-raid@vger.kernel.org
Subject: PATCH - md 9 of 22 - Discard functions that have been "not yet" for a long time
Date: Wed, 19 Jun 2002 10:51:44 +1000 (EST) [thread overview]
Message-ID: <15631.54688.95261.464387@notabene.cse.unsw.edu.au> (raw)
Discard functions that have been "not yet" for a long time
It is not clear what these should do, or if they will ever be
needed, so let's clean them out. They can easily be recreated
if there is a need.
----------- Diffstat output ------------
./drivers/md/md.c | 50 --------------------------------------------------
1 files changed, 50 deletions(-)
--- ./drivers/md/md.c 2002/06/18 04:18:33 1.8
+++ ./drivers/md/md.c 2002/06/18 04:20:52 1.9
@@ -2503,36 +2503,6 @@
}
#undef SET_SB
-static int set_disk_info(mddev_t * mddev, void * arg)
-{
- printk(KERN_INFO "md: not yet");
- return -EINVAL;
-}
-
-static int clear_array(mddev_t * mddev)
-{
- printk(KERN_INFO "md: not yet");
- return -EINVAL;
-}
-
-static int write_raid_info(mddev_t * mddev)
-{
- printk(KERN_INFO "md: not yet");
- return -EINVAL;
-}
-
-static int protect_array(mddev_t * mddev)
-{
- printk(KERN_INFO "md: not yet");
- return -EINVAL;
-}
-
-static int unprotect_array(mddev_t * mddev)
-{
- printk(KERN_INFO "md: not yet");
- return -EINVAL;
-}
-
static int set_disk_faulty(mddev_t *mddev, kdev_t dev)
{
mdk_rdev_t *rdev;
@@ -2767,10 +2737,6 @@
switch (cmd)
{
- case CLEAR_ARRAY:
- err = clear_array(mddev);
- goto done_unlock;
-
case ADD_NEW_DISK:
{
mdu_disk_info_t info;
@@ -2789,22 +2755,6 @@
case HOT_ADD_DISK:
err = hot_add_disk(mddev, val_to_kdev(arg));
- goto done_unlock;
-
- case SET_DISK_INFO:
- err = set_disk_info(mddev, (void *)arg);
- goto done_unlock;
-
- case WRITE_RAID_INFO:
- err = write_raid_info(mddev);
- goto done_unlock;
-
- case UNPROTECT_ARRAY:
- err = unprotect_array(mddev);
- goto done_unlock;
-
- case PROTECT_ARRAY:
- err = protect_array(mddev);
goto done_unlock;
case SET_DISK_FAULTY:
reply other threads:[~2002-06-19 0:51 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=15631.54688.95261.464387@notabene.cse.unsw.edu.au \
--to=neilb@cse.unsw.edu.au \
--cc=linux-raid@vger.kernel.org \
--cc=torvalds@transmeta.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).