From: Randy Dunlap <rdunlap@infradead.org>
To: Linux FS Devel <linux-fsdevel@vger.kernel.org>,
Miklos Szeredi <miklos@szeredi.hu>
Subject: [PATCH -next] fuse: fix virtio_fs.c build warnings
Date: Fri, 30 Aug 2019 16:29:33 -0700 [thread overview]
Message-ID: <4dbb6d9e-846f-e566-30a4-0082dd113bd3@infradead.org> (raw)
From: Randy Dunlap <rdunlap@infradead.org>
Be consistent in using CONFIG_PM_SLEEP for the freeze and restore
functions to avoid build warnings.
../fs/fuse/virtio_fs.c:501:12: warning: ‘virtio_fs_restore’ defined but not used [-Wunused-function]
static int virtio_fs_restore(struct virtio_device *vdev)
^~~~~~~~~~~~~~~~~
../fs/fuse/virtio_fs.c:496:12: warning: ‘virtio_fs_freeze’ defined but not used [-Wunused-function]
static int virtio_fs_freeze(struct virtio_device *vdev)
^~~~~~~~~~~~~~~~
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Miklos Szeredi <miklos@szeredi.hu>
Cc: linux-fsdevel@vger.kernel.org
---
fs/fuse/virtio_fs.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
--- linux-next-20190830.orig/fs/fuse/virtio_fs.c
+++ linux-next-20190830/fs/fuse/virtio_fs.c
@@ -492,7 +492,7 @@ static void virtio_fs_remove(struct virt
vdev->priv = NULL;
}
-#ifdef CONFIG_PM
+#ifdef CONFIG_PM_SLEEP
static int virtio_fs_freeze(struct virtio_device *vdev)
{
return 0; /* TODO */
@@ -502,7 +502,7 @@ static int virtio_fs_restore(struct virt
{
return 0; /* TODO */
}
-#endif /* CONFIG_PM */
+#endif /* CONFIG_PM_SLEEP */
const static struct virtio_device_id id_table[] = {
{ VIRTIO_ID_FS, VIRTIO_DEV_ANY_ID },
reply other threads:[~2019-08-30 23:29 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=4dbb6d9e-846f-e566-30a4-0082dd113bd3@infradead.org \
--to=rdunlap@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=miklos@szeredi.hu \
/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.