public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Jakub Wilk <jwilk@jwilk.net>,
	"G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: Peter Xu <peterx@redhat.com>, linux-man@vger.kernel.org
Subject: Re: [PATCH v2 0/2] userfaultfd.2: Update to latest
Date: Tue, 7 Jun 2022 11:23:37 +0200	[thread overview]
Message-ID: <2868d619-8ed5-4dbc-cb62-751f36885c28@gmail.com> (raw)
In-Reply-To: <20220607091743.qx5ngkcmjnte7wld@jwilk.net>


[-- Attachment #1.1: Type: text/plain, Size: 1223 bytes --]

Hi Jakub!

On 6/7/22 11:17, Jakub Wilk wrote:
> * G. Branden Robinson <g.branden.robinson@gmail.com>, 2022-06-06, 16:33:
>> At 2022-06-06T15:40:08-0400, Peter Xu wrote:
>>>> I think the patch below would improve a little bit the wording (and 
>>>> newlines).  I still have a bit of trouble understanding "When a 
>>>> kernel-originated fault was triggered on the registered range with 
>>>> this userfaultfd".  Did you maybe mean "range registered" instead of 
>>>> "registered range"?
>>>
>>> Since I'm not a native speaker I don't immediately see the difference 
>>> between the two.
>>
>> Short answer: I think your existing wording is acceptable.
> 
> I think you missed the context. You get a different parse tree when you 
> swap the words:
> 
>    ...triggered (on the registered range) (with this userfaultfd).
> 
> vs
> 
>    ...triggered (on the range (registered with this userfaultfd)).
> 

Thanks, that's a very nice way to show it!  It may help Peter too. 
Basically, the places where you can parenthesize sentences as if they 
were mathematical expressions is where lines breaks should go :)


Cheers,

Alex

-- 
Alejandro Colomar
<http://www.alejandro-colomar.es/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-06-07  9:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-03 17:37 [PATCH v2 0/2] userfaultfd.2: Update to latest Peter Xu
2022-06-03 17:37 ` [PATCH v2 1/2] userfaultfd.2: Add section for UFFD_USER_MODE_ONLY Peter Xu
2022-06-03 17:37 ` [PATCH v2 2/2] userfaultfd.2: Update on write-protection support Peter Xu
2022-06-06 18:52 ` [PATCH v2 0/2] userfaultfd.2: Update to latest Alejandro Colomar
2022-06-06 19:40   ` Peter Xu
2022-06-06 21:33     ` G. Branden Robinson
2022-06-07  9:08       ` Alejandro Colomar
2022-06-07 14:29         ` Peter Xu
2022-06-15 13:39           ` Alejandro Colomar
2022-06-15 15:00             ` Peter Xu
2022-06-07  9:17       ` Jakub Wilk
2022-06-07  9:23         ` Alejandro Colomar [this message]
2022-06-06 22:26     ` Axel Rasmussen

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=2868d619-8ed5-4dbc-cb62-751f36885c28@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=g.branden.robinson@gmail.com \
    --cc=jwilk@jwilk.net \
    --cc=linux-man@vger.kernel.org \
    --cc=peterx@redhat.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