From: kernel test robot <lkp@intel.com>
To: kbuild-all@lists.01.org
Subject: [RFC PATCH sashal-linux-stable] xfs: xfs_rtalloc_log_count can be static
Date: Sun, 27 Sep 2020 11:55:27 +0800 [thread overview]
Message-ID: <20200927035527.GA60792@501668ae326e> (raw)
In-Reply-To: <202009271148.RuHSFY5K%lkp@intel.com>
[-- Attachment #1: Type: text/plain, Size: 717 bytes --]
Fixes: 3620c7ff04a4 ("xfs: fix log reservation overflows when allocating large rt extents")
Signed-off-by: kernel test robot <lkp@intel.com>
---
xfs_trans_resv.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/xfs/libxfs/xfs_trans_resv.c b/fs/xfs/libxfs/xfs_trans_resv.c
index b3584cd2cc1640..a9b32879a9d15b 100644
--- a/fs/xfs/libxfs/xfs_trans_resv.c
+++ b/fs/xfs/libxfs/xfs_trans_resv.c
@@ -202,7 +202,7 @@ xfs_calc_inode_chunk_res(
* blocks as needed to mark inuse MAXEXTLEN blocks' worth of realtime extents,
* as well as the realtime summary block.
*/
-unsigned int
+static unsigned int
xfs_rtalloc_log_count(
struct xfs_mount *mp,
unsigned int num_ops)
prev parent reply other threads:[~2020-09-27 3:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-27 3:55 [sashal-linux-stable:queue-5.4 75/341] fs/xfs/libxfs/xfs_trans_resv.c:206:1: sparse: sparse: symbol 'xfs_rtalloc_log_count' was not declared. Should it be kernel test robot
2020-09-27 3:55 ` kernel test robot [this message]
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=20200927035527.GA60792@501668ae326e \
--to=lkp@intel.com \
--cc=kbuild-all@lists.01.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 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.