From: Hauke Mehrtens <hauke@hauke-m.de>
To: hch@infradead.org
Cc: linux-kernel@vger.kernel.org, ak@linux.intel.com,
Hauke Mehrtens <hauke@hauke-m.de>
Subject: [PATCH] freevxfs: Do not inline vxfs_put_page()
Date: Sat, 16 Jun 2018 17:44:09 +0200 [thread overview]
Message-ID: <20180616154409.26271-1-hauke@hauke-m.de> (raw)
vxfs_put_page() is not implemented in a header file, but in a normal c
file and used in multiple functions in different c files. Remove the
inline attribute as it does not make sense here and causes a link error
when LTO is activated.
Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
---
fs/freevxfs/vxfs_subr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/freevxfs/vxfs_subr.c b/fs/freevxfs/vxfs_subr.c
index e806694d4145..8e213cce586f 100644
--- a/fs/freevxfs/vxfs_subr.c
+++ b/fs/freevxfs/vxfs_subr.c
@@ -46,7 +46,7 @@ const struct address_space_operations vxfs_aops = {
.bmap = vxfs_bmap,
};
-inline void
+void
vxfs_put_page(struct page *pp)
{
kunmap(pp);
--
2.11.0
reply other threads:[~2018-06-16 15:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20180616154409.26271-1-hauke@hauke-m.de \
--to=hauke@hauke-m.de \
--cc=ak@linux.intel.com \
--cc=hch@infradead.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;
as well as URLs for NNTP newsgroup(s).