From: Bernd Schubert <bschubert@ddn.com>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
"bernd@bsbernd.com" <bernd@bsbernd.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-next@vger.kernel.org" <linux-next@vger.kernel.org>
Subject: Re: [PATCH] fuse: Fix Documentation/filesystems/fuse-io-uring.rst
Date: Tue, 21 Jan 2025 11:15:33 +0000 [thread overview]
Message-ID: <3eb0dff2-d51c-4037-84d4-281e8534d1b1@ddn.com> (raw)
In-Reply-To: <CAJfpeguaLKfh8T1z+YSzkzgvLBmHNXkRQU0qOAyVQdWeABg+_A@mail.gmail.com>
On 1/21/25 10:27, Miklos Szeredi wrote:
> On Tue, 21 Jan 2025 at 09:38, Bernd Schubert <bschubert@ddn.com> wrote:
>>
>> This adds several documentation updates I had missed after
>> renaming functions and also fixes 'make htmldocs'.
>>
>> Signed-off-by: Bernd Schubert <bschubert@ddn.com>
>
> Folded into docs patch.
>
Thank you Miklos!
prev parent reply other threads:[~2025-01-21 11:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-21 6:48 linux-next: build warnings after merge of the fuse tree Stephen Rothwell
2025-01-21 8:37 ` [PATCH] fuse: Fix Documentation/filesystems/fuse-io-uring.rst Bernd Schubert
2025-01-21 9:27 ` Miklos Szeredi
2025-01-21 11:15 ` Bernd Schubert [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=3eb0dff2-d51c-4037-84d4-281e8534d1b1@ddn.com \
--to=bschubert@ddn.com \
--cc=bernd@bsbernd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=sfr@canb.auug.org.au \
/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