From: Al Viro <viro@zeniv.linux.org.uk>
To: Matthew Wilcox <willy@infradead.org>
Cc: Xiaofeng Cao <cxfcosmos@gmail.com>,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
Xiaofeng Cao <caoxiaofeng@yulong.com>
Subject: Re: [PATCH] fs/dcache: fix typos and sentence disorder
Date: Thu, 18 Mar 2021 16:35:34 +0000 [thread overview]
Message-ID: <YFOBVg8UiQh4Z4II@zeniv-ca.linux.org.uk> (raw)
In-Reply-To: <20210318150020.GP3420@casper.infradead.org>
On Thu, Mar 18, 2021 at 03:00:20PM +0000, Matthew Wilcox wrote:
> On Thu, Mar 18, 2021 at 10:31:53PM +0800, Xiaofeng Cao wrote:
> > change 'sould' to 'should'
> > change 'colocated' to 'collocated'
>
> uh. collocated is incorrect. colocated is correct.
> https://www.merriam-webster.com/dictionary/colocate
> https://www.merriam-webster.com/dictionary/collocate
A bit more condensed variant: these two are both derived from
con- + loco, but have different meanings -
colocated: occupying the same place
collocated: sitting next to each other
In this case it's very much the former - the point of comment is that
the fields in question share the same memory location, but we are
guaranteed that any dentry we find in the alias list of an inode will
have that location used for ->i_dentry.
"co-located" would probably work better there.
PS: history of that word pair is amusing. Both are (English) past participles,
of co-locate and collocate resp. The former had the (Latin) prefix applied in
English to borrowing from Latin (co-locate < locate < locatus) , the latter
is straight borrowing (collocate < collocatus). Incidentally, in both cases
the borrowed form had already been a past participle (of loco and
colloco) resp. And colloco had the same prefix (com-/con-/co-) applied
in Latin, with regular assimilation of -nl- to -ll-. But at that stage
the meaning of the verb had been closer to "put in place" than to
"be in place", so that gave "put next to each other" instead of "share
the place". Shift towards "be found next to each other" happened long after
the prefix had been applied...
next prev parent reply other threads:[~2021-03-18 16:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-18 14:31 Xiaofeng Cao
2021-03-18 15:00 ` Matthew Wilcox
2021-03-18 16:35 ` Al Viro [this message]
2021-03-18 16:50 ` Christian Brauner
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=YFOBVg8UiQh4Z4II@zeniv-ca.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=caoxiaofeng@yulong.com \
--cc=cxfcosmos@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=willy@infradead.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
all inboxes | Powered by JetHome®