From: "Luis R. Rodriguez" <mcgrof@kernel.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Matthew Wilcox <willy@infradead.org>,
David Howells <dhowells@redhat.com>,
"Luis R. Rodriguez" <mcgrof@kernel.org>,
tglx@linutronix.de, arnd@arndb.de, cl@linux.com,
keescook@chromium.org, luto@amacapital.net, longman@redhat.com,
viro@zeniv.linux.org.uk, ebiederm@xmission.com,
linux-arch@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: expland documentation over __read_mostly
Date: Tue, 8 May 2018 18:17:06 +0000 [thread overview]
Message-ID: <20180508181706.GI27853@wotan.suse.de> (raw)
In-Reply-To: <7d6664dc-01f5-55d9-d309-0378ff609b8a@infradead.org>
On Tue, May 08, 2018 at 08:39:30AM -0700, Randy Dunlap wrote:
> On 05/08/2018 04:23 AM, Matthew Wilcox wrote:
> > On Tue, May 08, 2018 at 09:28:14AM +0100, David Howells wrote:
> >> Randy Dunlap <rdunlap@infradead.org> wrote:
> >>
> >>>> + * execute a critial path. We should be mindful and selective if its use.
> >>>
> >>> of its use.
> >>
> >> in its use.
> > with its use.
> >
> > Nah, just kidding. Let's go with "in".
> >
>
> Yeah, no, I don't care. Just flip a 3-sided coin.
Heh, the coin says "of".
I also added:
* ie: if you're going to use it please supply a *good* justification in your
* commit log.
Sending v2.
Luis
next prev parent reply other threads:[~2018-05-08 18:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-07 23:15 [PATCH] mm: expland documentation over __read_mostly Luis R. Rodriguez
2018-05-08 0:20 ` Randy Dunlap
2018-05-08 3:23 ` Joel Fernandes
2018-05-08 8:28 ` David Howells
2018-05-08 11:23 ` Matthew Wilcox
2018-05-08 15:39 ` Randy Dunlap
2018-05-08 18:17 ` Luis R. Rodriguez [this message]
2018-05-08 12:54 ` Christopher Lameter
2020-05-06 23:13 Luis Chamberlain
2020-05-06 23:36 ` Rafael Aquini
2020-05-06 23:44 ` Matthew Wilcox
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=20180508181706.GI27853@wotan.suse.de \
--to=mcgrof@kernel.org \
--cc=arnd@arndb.de \
--cc=cl@linux.com \
--cc=dhowells@redhat.com \
--cc=ebiederm@xmission.com \
--cc=keescook@chromium.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=longman@redhat.com \
--cc=luto@amacapital.net \
--cc=rdunlap@infradead.org \
--cc=tglx@linutronix.de \
--cc=viro@zeniv.linux.org.uk \
--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;
as well as URLs for NNTP newsgroup(s).