public inbox for linux-doc@vger.kernel.org
 help / color / mirror / Atom feed
From: "Guilherme G. Piccoli" <gpiccoli@igalia.com>
To: "Darrick J. Wong" <djwong@kernel.org>, Jens Axboe <axboe@kernel.dk>
Cc: linux-doc@vger.kernel.org, corbet@lwn.net,
	linux-fsdevel@vger.kernel.org, linux-block@vger.kernel.org,
	kernel-dev@igalia.com, kernel@gpiccoli.net,
	Bart Van Assche <bvanassche@acm.org>, Jan Kara <jack@suse.cz>
Subject: Re: [PATCH V3] Documentation: Document the kernel flag bdev_allow_write_mounted
Date: Sun, 25 Aug 2024 21:17:09 -0300	[thread overview]
Message-ID: <87bcaf5a-f5dd-fa0d-1936-665516cee100@igalia.com> (raw)
In-Reply-To: <20240823184225.GA6082@frogsfrogsfrogs>

On 23/08/2024 15:42, Darrick J. Wong wrote:
> [...]
>> Since we're nit picking...
>>
>> Control the ability to directly write [...]
>>
>> The directly may be a bit confusing ("does it mean O_DIRECT?"), so maybe
>> just
>>
>> Control the ability to write [...]
>>
>> would be better and more clear.
> 
> "Control the ability to open a block device for writing."
> 
> Since that's what it actually does, right?
> 
> --D
> 
>>> +			devices, i.e., allow / disallow writes that bypasses the
>>
>> Since we're nit picking, s/bypasses/bypass
>>

Thank you both! Just sent the V4

      reply	other threads:[~2024-08-26  0:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-23 18:05 [PATCH V3] Documentation: Document the kernel flag bdev_allow_write_mounted Guilherme G. Piccoli
2024-08-23 18:17 ` Jens Axboe
2024-08-23 18:42   ` Darrick J. Wong
2024-08-26  0:17     ` Guilherme G. Piccoli [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=87bcaf5a-f5dd-fa0d-1936-665516cee100@igalia.com \
    --to=gpiccoli@igalia.com \
    --cc=axboe@kernel.dk \
    --cc=bvanassche@acm.org \
    --cc=corbet@lwn.net \
    --cc=djwong@kernel.org \
    --cc=jack@suse.cz \
    --cc=kernel-dev@igalia.com \
    --cc=kernel@gpiccoli.net \
    --cc=linux-block@vger.kernel.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.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