From: Marcos Paulo de Souza <marcos.souza.org@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: Marcos Paulo de Souza <marcos.souza.org@gmail.com>,
Shaohua Li <shli@kernel.org>,
linux-raid@vger.kernel.org (open list:SOFTWARE RAID (Multiple
Disks) SUPPORT)
Subject: [PATCH 3/4] md: raid0: Return md_integrity_register result directly
Date: Mon, 20 May 2019 18:44:26 -0300 [thread overview]
Message-ID: <20190520214427.18729-4-marcos.souza.org@gmail.com> (raw)
In-Reply-To: <20190520214427.18729-1-marcos.souza.org@gmail.com>
Commit 0c35bd4723e4a39ba2da4c13a22cb97986ee10c8
("md: fix problems with freeing private data after ->run failure")
removed the check for the result of md_integrity_register, so we don't
need to store it anymore, so return it directly.
Signed-off-by: Marcos Paulo de Souza <marcos.souza.org@gmail.com>
---
drivers/md/raid0.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/md/raid0.c b/drivers/md/raid0.c
index 42b0287104bd..e72255464c09 100644
--- a/drivers/md/raid0.c
+++ b/drivers/md/raid0.c
@@ -431,9 +431,7 @@ static int raid0_run(struct mddev *mddev)
dump_zones(mddev);
- ret = md_integrity_register(mddev);
-
- return ret;
+ return md_integrity_register(mddev);
}
static void raid0_free(struct mddev *mddev, void *priv)
--
2.21.0
next prev parent reply other threads:[~2019-05-20 21:44 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-20 21:44 [PATCH 0/5] raid1-10 and raid0 cleanups Marcos Paulo de Souza
2019-05-20 21:44 ` [PATCH 1/4] md: raid1-10: Unify r{1,10}bio_pool_free Marcos Paulo de Souza
2019-05-20 21:44 ` [PATCH 2/4] md: raid0: Remove return statement from void function Marcos Paulo de Souza
2019-05-21 5:53 ` Song Liu
2019-05-20 21:44 ` Marcos Paulo de Souza [this message]
2019-05-20 21:44 ` [PATCH 4/4] md: raid0: Make ret local in raid0_run Marcos Paulo de Souza
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=20190520214427.18729-4-marcos.souza.org@gmail.com \
--to=marcos.souza.org@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=shli@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
all inboxes | Powered by JetHome®