From: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
To: msakai@redhat.com
Cc: dm-devel@lists.linux.dev, linux-kernel@vger.kernel.org,
Jiapeng Chong <jiapeng.chong@linux.alibaba.com>,
Abaci Robot <abaci@linux.alibaba.com>
Subject: [PATCH 1/8] dm vdo: Modify mismatched function name
Date: Wed, 21 Feb 2024 17:17:31 +0800 [thread overview]
Message-ID: <20240221091731.7007-8-jiapeng.chong@linux.alibaba.com> (raw)
In-Reply-To: <20240221091731.7007-1-jiapeng.chong@linux.alibaba.com>
No functional modification involved.
drivers/md/dm-vdo/vdo.c:276: warning: expecting prototype for vdo_read_geometry_block(). Prototype was for read_geometry_block() instead.
Reported-by: Abaci Robot <abaci@linux.alibaba.com>
Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=8273
Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
---
drivers/md/dm-vdo/vdo.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/md/dm-vdo/vdo.c b/drivers/md/dm-vdo/vdo.c
index 23a4f1d1b6dc..411c58341173 100644
--- a/drivers/md/dm-vdo/vdo.c
+++ b/drivers/md/dm-vdo/vdo.c
@@ -266,7 +266,7 @@ static int __must_check initialize_thread_config(struct thread_count_config coun
}
/**
- * vdo_read_geometry_block() - Synchronously read the geometry block from a vdo's underlying block
+ * read_geometry_block() - Synchronously read the geometry block from a vdo's underlying block
* device.
* @vdo: The vdo whose geometry is to be read.
*
--
2.20.1.7.g153144c
next prev parent reply other threads:[~2024-02-21 9:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-21 9:17 [PATCH 8/8] " Jiapeng Chong
2024-02-21 9:17 ` [PATCH 7/8] dm vdo dedupe: " Jiapeng Chong
2024-02-21 9:17 ` [PATCH 6/8] dm vdo: " Jiapeng Chong
2024-02-21 9:17 ` [PATCH 5/8] " Jiapeng Chong
2024-02-21 9:17 ` [PATCH 4/8] " Jiapeng Chong
2024-02-21 9:17 ` [PATCH 3/8] " Jiapeng Chong
2024-02-21 9:17 ` [PATCH 2/8] " Jiapeng Chong
2024-02-21 9:17 ` Jiapeng Chong [this message]
2024-02-22 17:15 ` [PATCH 1/8] " Matthew Sakai
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=20240221091731.7007-8-jiapeng.chong@linux.alibaba.com \
--to=jiapeng.chong@linux.alibaba.com \
--cc=abaci@linux.alibaba.com \
--cc=dm-devel@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=msakai@redhat.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
all inboxes | Powered by JetHome®