From: Miklos Szeredi <miklos@szeredi.hu>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org,
Miklos Szeredi <mszeredi@redhat.com>,
linux-fsdevel@vger.kernel.org,
Chen Linxuan <chenlinxuan@uniontech.com>
Subject: Re: [PATCH] fuse: dev: avoid a build warning when PROC_FS is not set
Date: Thu, 15 May 2025 11:08:30 +0200 [thread overview]
Message-ID: <CAJfpegv9k5tPwq66yRvA6EdFaxHUqGsxYCfxnAKg8HjwpTi_gw@mail.gmail.com> (raw)
In-Reply-To: <20250514213243.3685364-1-rdunlap@infradead.org>
On Wed, 14 May 2025 at 23:32, Randy Dunlap <rdunlap@infradead.org> wrote:
>
> Fix a build warning when CONFIG_PROC_FS is not set by surrounding the
> function with #ifdef CONFIG_PROC_FS.
>
> fs/fuse/dev.c:2620:13: warning: 'fuse_dev_show_fdinfo' defined but not used [-Wunused-function]
> 2620 | static void fuse_dev_show_fdinfo(struct seq_file *seq, struct file *file)
>
> Fixes: 514d9210bf45 ("fs: fuse: add dev id to /dev/fuse fdinfo")
> Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Folded, thanks.
Miklos
prev parent reply other threads:[~2025-05-15 9:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 21:32 [PATCH] fuse: dev: avoid a build warning when PROC_FS is not set Randy Dunlap
2025-05-15 2:10 ` Chen Linxuan
2025-05-15 9:08 ` Miklos Szeredi [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=CAJfpegv9k5tPwq66yRvA6EdFaxHUqGsxYCfxnAKg8HjwpTi_gw@mail.gmail.com \
--to=miklos@szeredi.hu \
--cc=chenlinxuan@uniontech.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mszeredi@redhat.com \
--cc=rdunlap@infradead.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).