The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jonathan Corbet <corbet@lwn.net>
To: Amir Goldstein <amir73il@gmail.com>, chenlinxuan@uniontech.com
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
	linux-doc@vger.kernel.org,
	Bernd Schubert <bernd.schubert@fastmail.fm>,
	Bagas Sanjaya <bagasdotme@gmail.com>
Subject: Re: [PATCH 2/2] docs: filesystems: add fuse-passthrough.rst
Date: Mon, 19 May 2025 09:02:11 -0600	[thread overview]
Message-ID: <87tt5giqz0.fsf@trenco.lwn.net> (raw)
In-Reply-To: <CAOQ4uxiMh+3JqzqMbK+HpFt-hWaM6A2nW3UHNK9nNntDRkRBeQ@mail.gmail.com>

Amir Goldstein <amir73il@gmail.com> writes:

> On Wed, May 7, 2025 at 7:17 AM Chen Linxuan via B4 Relay
> <devnull+chenlinxuan.uniontech.com@kernel.org> wrote:
>>
>> From: Chen Linxuan <chenlinxuan@uniontech.com>
>>
>> Add a documentation about FUSE passthrough.
>>
>> It's mainly about why FUSE passthrough needs CAP_SYS_ADMIN.
>>
>
> Hi Chen,
>
> Thank you for this contribution!
>
> Very good summary.
> with minor nits below fix you may add to both patches:
>
> Reviewed-by: Amir Goldstein <amir73il@gmail.com>

It looks like these comments were never addressed ... ?

Thanks,

jon

  reply	other threads:[~2025-05-19 15:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-07  5:16 [PATCH 0/2] Add a documentation for FUSE passthrough Chen Linxuan via B4 Relay
2025-05-07  5:16 ` [PATCH 1/2] MAINTAINERS: update filter of FUSE documentation Chen Linxuan via B4 Relay
2025-05-07  5:16 ` [PATCH 2/2] docs: filesystems: add fuse-passthrough.rst Chen Linxuan via B4 Relay
2025-05-07  7:05   ` Bagas Sanjaya
2025-05-07  8:17   ` Amir Goldstein
2025-05-19 15:02     ` Jonathan Corbet [this message]
2025-05-20  1:49       ` Chen Linxuan

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=87tt5giqz0.fsf@trenco.lwn.net \
    --to=corbet@lwn.net \
    --cc=amir73il@gmail.com \
    --cc=bagasdotme@gmail.com \
    --cc=bernd.schubert@fastmail.fm \
    --cc=chenlinxuan@uniontech.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox