From: Chengsong Ke <kechengsong@huawei.com> To: <richard@nod.at>, <s.hauer@pengutronix.de> Cc: <linux-mtd@lists.infradead.org>, <linux-kernel@vger.kernel.org>, <wangfangpeng1@huawei.com> Subject: [PATCH] ubifs: Remove the redundant return in dbg_check_nondata_nodes_order Date: Mon, 2 Nov 2020 16:27:43 +0800 [thread overview] Message-ID: <20201102082743.34172-1-kechengsong@huawei.com> (raw) There is a redundant return in dbg_check_nondata_nodes_order, which will be never reached. In addition, error code should be returned instead of zero in this branch. Signed-off-by: Chengsong Ke <kechengsong@huawei.com> --- fs/ubifs/debug.c | 1 - 1 file changed, 1 deletion(-) diff --git a/fs/ubifs/debug.c b/fs/ubifs/debug.c index ebff43f8009c..b2db518056cb 100644 --- a/fs/ubifs/debug.c +++ b/fs/ubifs/debug.c @@ -2442,7 +2442,6 @@ int dbg_check_nondata_nodes_order(struct ubifs_info *c, struct list_head *head) ubifs_msg(c, "dumping second node"); ubifs_dump_node(c, sb->node); return -EINVAL; - return 0; } static inline int chance(unsigned int n, unsigned int out_of) -- 2.12.3
WARNING: multiple messages have this Message-ID (diff)
From: Chengsong Ke <kechengsong@huawei.com> To: <richard@nod.at>, <s.hauer@pengutronix.de> Cc: linux-mtd@lists.infradead.org, linux-kernel@vger.kernel.org, wangfangpeng1@huawei.com Subject: [PATCH] ubifs: Remove the redundant return in dbg_check_nondata_nodes_order Date: Mon, 2 Nov 2020 16:27:43 +0800 [thread overview] Message-ID: <20201102082743.34172-1-kechengsong@huawei.com> (raw) There is a redundant return in dbg_check_nondata_nodes_order, which will be never reached. In addition, error code should be returned instead of zero in this branch. Signed-off-by: Chengsong Ke <kechengsong@huawei.com> --- fs/ubifs/debug.c | 1 - 1 file changed, 1 deletion(-) diff --git a/fs/ubifs/debug.c b/fs/ubifs/debug.c index ebff43f8009c..b2db518056cb 100644 --- a/fs/ubifs/debug.c +++ b/fs/ubifs/debug.c @@ -2442,7 +2442,6 @@ int dbg_check_nondata_nodes_order(struct ubifs_info *c, struct list_head *head) ubifs_msg(c, "dumping second node"); ubifs_dump_node(c, sb->node); return -EINVAL; - return 0; } static inline int chance(unsigned int n, unsigned int out_of) -- 2.12.3 ______________________________________________________ Linux MTD discussion mailing list http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2020-11-02 8:27 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-02 8:27 Chengsong Ke [this message] 2020-11-02 8:27 ` [PATCH] ubifs: Remove the redundant return in dbg_check_nondata_nodes_order Chengsong Ke 2020-12-11 3:34 ` Chengsong Ke 2020-12-11 3:34 ` Chengsong Ke
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=20201102082743.34172-1-kechengsong@huawei.com \ --to=kechengsong@huawei.com \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mtd@lists.infradead.org \ --cc=richard@nod.at \ --cc=s.hauer@pengutronix.de \ --cc=wangfangpeng1@huawei.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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.