From: Miklos Szeredi <miklos@szeredi.hu>
To: Luis Henriques <luis@igalia.com>
Cc: Bernd Schubert <bschubert@ddn.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] fuse: removed unused function fuse_uring_create() from header
Date: Fri, 14 Feb 2025 10:48:27 +0100 [thread overview]
Message-ID: <CAJfpegsymDHQj800wtD6Tq9fSOHjJ+UJ7dhvPf9Ut0LT71us4g@mail.gmail.com> (raw)
In-Reply-To: <20250207133502.24209-1-luis@igalia.com>
On Fri, 7 Feb 2025 at 14:35, Luis Henriques <luis@igalia.com> wrote:
>
> Function fuse_uring_create() is used only from dev_uring.c and does not
> need to be exposed in the header file. Furthermore, it has the wrong
> signature.
>
> While there, also remove the 'struct fuse_ring' forward declaration.
Applied, thanks.
Miklos
prev parent reply other threads:[~2025-02-14 9:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 13:35 [PATCH] fuse: removed unused function fuse_uring_create() from header Luis Henriques
2025-02-07 13:42 ` Bernd Schubert
2025-02-14 9:48 ` 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=CAJfpegsymDHQj800wtD6Tq9fSOHjJ+UJ7dhvPf9Ut0LT71us4g@mail.gmail.com \
--to=miklos@szeredi.hu \
--cc=bschubert@ddn.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luis@igalia.com \
/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).