From: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
To: kent.overstreet@linux.dev
Cc: bfoster@redhat.com, linux-bcachefs@vger.kernel.org,
linux-kernel@vger.kernel.org,
Jiapeng Chong <jiapeng.chong@linux.alibaba.com>,
Abaci Robot <abaci@linux.alibaba.com>
Subject: [PATCH 1/9] bcachefs: Modify mismatched function name
Date: Thu, 14 Sep 2023 17:04:50 +0800 [thread overview]
Message-ID: <20230914090457.32325-2-jiapeng.chong@linux.alibaba.com> (raw)
In-Reply-To: <20230914090457.32325-1-jiapeng.chong@linux.alibaba.com>
No functional modification involved.
fs/bcachefs/journal_reclaim.c:600: warning: expecting prototype for bch2_journal_reclaim(). Prototype was for __bch2_journal_reclaim() instead.
Reported-by: Abaci Robot <abaci@linux.alibaba.com>
Closes: https://bugzilla.openanolis.cn/show_bug.cgi?id=6576
Signed-off-by: Jiapeng Chong <jiapeng.chong@linux.alibaba.com>
---
fs/bcachefs/journal_reclaim.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/bcachefs/journal_reclaim.c b/fs/bcachefs/journal_reclaim.c
index 10e1860dad79..bed94af68fd0 100644
--- a/fs/bcachefs/journal_reclaim.c
+++ b/fs/bcachefs/journal_reclaim.c
@@ -579,7 +579,7 @@ static u64 journal_seq_to_flush(struct journal *j)
}
/**
- * bch2_journal_reclaim - free up journal buckets
+ * __bch2_journal_reclaim - free up journal buckets
*
* Background journal reclaim writes out btree nodes. It should be run
* early enough so that we never completely run out of journal buckets.
--
2.20.1.7.g153144c
next prev parent reply other threads:[~2023-09-14 9:05 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-14 9:04 [PATCH 9/9] " Jiapeng Chong
2023-09-14 9:04 ` Jiapeng Chong [this message]
2023-09-14 9:04 ` [PATCH 2/9] " Jiapeng Chong
2023-09-14 9:04 ` [PATCH 3/9] " Jiapeng Chong
2023-09-14 9:04 ` [PATCH 4/9] " Jiapeng Chong
2023-09-14 9:04 ` [PATCH 5/9] " Jiapeng Chong
2023-09-14 9:04 ` [PATCH 6/9] " Jiapeng Chong
2023-09-14 9:04 ` [PATCH 7/9] " Jiapeng Chong
2023-09-14 9:04 ` [PATCH 8/9] " Jiapeng Chong
2023-09-14 12:18 ` [PATCH 9/9] " Brian Foster
2023-09-14 19:49 ` Kent Overstreet
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=20230914090457.32325-2-jiapeng.chong@linux.alibaba.com \
--to=jiapeng.chong@linux.alibaba.com \
--cc=abaci@linux.alibaba.com \
--cc=bfoster@redhat.com \
--cc=kent.overstreet@linux.dev \
--cc=linux-bcachefs@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®