From: NeilBrown <neilb@suse.com>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
Al Viro <viro@ZenIV.linux.org.uk>,
lkml <linux-kernel@vger.kernel.org>,
"J. Bruce Fields" <bfields@fieldses.org>,
linux-doc@vger.kernel.org
Subject: Re: [PATCH] Documentation: add new description of path-name lookup.
Date: Thu, 6 Aug 2015 12:54:35 +1000 [thread overview]
Message-ID: <20150806125435.694d9ee3@noble> (raw)
In-Reply-To: <55B5A880.8040500@infradead.org>
On Sun, 26 Jul 2015 20:41:52 -0700 Randy Dunlap <rdunlap@infradead.org>
wrote:
> On 07/24/15 17:28, NeilBrown wrote:
> >
>
> Hi Neil,
>
> Some edits for you to consider.
Wow, thanks. I think I agree with all ... had to do some research for
"neither is" though.
>
> > +However, there is a little bit more to seqlocks than that. If
> > +RCU-walk accesses two different fields in a seqlock-protected
> > +structure, or accesses the same field twice, there is no a-priori
>
> no hyphen: ^
Do you have an opinion on where I should but "a priori" in italics?
I feel there needs to be something to make it clear the "a" is not an
English "a".
Jon: do you want an incremental patch, or a resend?
Thanks,
NeilBrown
next prev parent reply other threads:[~2015-08-06 2:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-25 0:28 [PATCH] Documentation: add new description of path-name lookup NeilBrown
2015-07-27 3:41 ` Randy Dunlap
2015-08-06 2:54 ` NeilBrown [this message]
2015-08-06 2:56 ` Randy Dunlap
2015-08-06 10:01 ` Jonathan Corbet
2015-10-26 6:35 ` [PATCHv2] " Neil Brown
2015-10-27 21:21 ` J. Bruce Fields
2015-10-27 23:12 ` Neil Brown
2015-11-03 1:19 ` Jonathan Corbet
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=20150806125435.694d9ee3@noble \
--to=neilb@suse.com \
--cc=bfields@fieldses.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=viro@ZenIV.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.