From: kbuild test robot <lkp@intel.com>
To: Ritesh Harjani <riteshh@linux.ibm.com>
Cc: kbuild-all@lists.01.org, jack@suse.cz, tytso@mit.edu,
linux-ext4@vger.kernel.org
Subject: [RFC PATCH] ext4: ext4_iomap_xattr_ops can be static
Date: Fri, 28 Feb 2020 03:18:49 +0800 [thread overview]
Message-ID: <20200227191849.GA79833@5ae7410f0801> (raw)
In-Reply-To: <2341a116e39ff0934b1f90aee8f4e10ac0371648.1582800839.git.riteshh@linux.ibm.com>
Fixes: e3d16669487e ("ext4: Move ext4_fiemap to use iomap framework.")
Signed-off-by: kbuild test robot <lkp@intel.com>
---
extents.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/ext4/extents.c b/fs/ext4/extents.c
index 204795232ce7e..42eeedd9db00c 100644
--- a/fs/ext4/extents.c
+++ b/fs/ext4/extents.c
@@ -4915,7 +4915,7 @@ static int ext4_iomap_xattr_begin(struct inode *inode, loff_t offset,
return error;
}
-const struct iomap_ops ext4_iomap_xattr_ops = {
+static const struct iomap_ops ext4_iomap_xattr_ops = {
.iomap_begin = ext4_iomap_xattr_begin,
};
next prev parent reply other threads:[~2020-02-28 1:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-27 11:10 [PATCHv4 0/6] ext4: bmap & fiemap conversion to use iomap Ritesh Harjani
2020-02-27 11:10 ` [PATCHv4 1/6] ext4: Add IOMAP_F_MERGED for non-extent based mapping Ritesh Harjani
2020-02-27 11:44 ` Jan Kara
2020-02-27 11:10 ` [PATCHv4 2/6] ext4: Optimize ext4_ext_precache for 0 depth Ritesh Harjani
2020-02-27 11:10 ` [PATCHv4 3/6] ext4: Move ext4 bmap to use iomap infrastructure Ritesh Harjani
2020-02-27 11:10 ` [PATCHv4 4/6] ext4: Make ext4_ind_map_blocks work with fiemap Ritesh Harjani
2020-02-27 11:49 ` Jan Kara
2020-02-27 11:10 ` [PATCHv4 5/6] ext4: Move ext4_fiemap to use iomap framework Ritesh Harjani
2020-02-27 11:58 ` Jan Kara
2020-02-27 19:18 ` kbuild test robot
2020-02-27 19:18 ` kbuild test robot [this message]
2020-02-27 11:10 ` [PATCHv4 6/6] Documentation: Correct the description of FIEMAP_EXTENT_LAST Ritesh Harjani
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=20200227191849.GA79833@5ae7410f0801 \
--to=lkp@intel.com \
--cc=jack@suse.cz \
--cc=kbuild-all@lists.01.org \
--cc=linux-ext4@vger.kernel.org \
--cc=riteshh@linux.ibm.com \
--cc=tytso@mit.edu \
/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