From: Lidong Zhong <lzhong@suse.com>
To: linux-raid@vger.kernel.org
Subject: [PATCH 1/3] config.c: since dlist is initialized as NULL, remove the useless code
Date: Thu, 27 Aug 2015 15:34:55 +0800 [thread overview]
Message-ID: <1440660897-7619-1-git-send-email-lzhong@suse.com> (raw)
Signed-off-by: Lidong Zhong <lzhong@suse.com>
---
config.c | 7 -------
1 file changed, 7 deletions(-)
diff --git a/config.c b/config.c
index c58c8fe..bb5af86 100644
--- a/config.c
+++ b/config.c
@@ -941,13 +941,6 @@ struct mddev_dev *conf_get_devs()
static struct mddev_dev *dlist = NULL;
unsigned int i;
- while (dlist) {
- struct mddev_dev *t = dlist;
- dlist = dlist->next;
- free(t->devname);
- free(t);
- }
-
load_conffile();
if (cdevlist == NULL) {
--
1.8.1.4
next reply other threads:[~2015-08-27 7:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-27 7:34 Lidong Zhong [this message]
2015-08-27 7:34 ` [PATCH 2/3] policy.c: make it easily understood when comparing the string Lidong Zhong
2015-08-27 7:34 ` [PATCH 3/3] mdadm: remove duplicate logic when c.delay is 0 Lidong Zhong
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=1440660897-7619-1-git-send-email-lzhong@suse.com \
--to=lzhong@suse.com \
--cc=linux-raid@vger.kernel.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).