From: Joel Fernandes <joel@joelfernandes.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: LKMM Maintainers -- Akira Yokosawa <akiyks@gmail.com>,
Andrea Parri <parri.andrea@gmail.com>,
Boqun Feng <boqun.feng@gmail.com>,
Daniel Lustig <dlustig@nvidia.com>,
David Howells <dhowells@redhat.com>,
Jade Alglave <j.alglave@ucl.ac.uk>,
Luc Maranget <luc.maranget@inria.fr>,
Nicholas Piggin <npiggin@gmail.com>,
"Paul E. McKenney" <paulmck@kernel.org>,
Peter Zijlstra <peterz@infradead.org>,
Will Deacon <will@kernel.org>,
Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] tools/memory-model/Documentation: Fix typos in explanation.txt
Date: Wed, 2 Oct 2019 11:11:16 -0400 [thread overview]
Message-ID: <20191002151116.GA88588@google.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1910021012541.1552-100000@iolanthe.rowland.org>
On Wed, Oct 02, 2019 at 10:13:43AM -0400, Alan Stern wrote:
> On Tue, 1 Oct 2019, Joel Fernandes wrote:
>
> > On Tue, Oct 01, 2019 at 01:39:47PM -0400, Alan Stern wrote:
> > > This patch fixes a few minor typos and improves word usage in a few
> > > places in the Linux Kernel Memory Model's explanation.txt file.
> > >
> > > Signed-off-by: Alan Stern <stern@rowland.harvard.edu>
> > >
> >
> > Reviewed-by: Joel Fernandes (Google) <joel@joelfernandes.org>
>
> Joel, if you're sufficiently interested in all this stuff, would you
> like to add yourself as a maintainer for the LKMM?
Absolutely I am quite interested. I will submit a patch for this. Thanks for
the suggestion, Alan!
thanks,
- Joel
prev parent reply other threads:[~2019-10-02 15:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-01 17:39 [PATCH 1/3] tools/memory-model/Documentation: Fix typos in explanation.txt Alan Stern
2019-10-01 21:01 ` Joel Fernandes
2019-10-01 22:30 ` Paul E. McKenney
2019-10-02 14:13 ` Alan Stern
2019-10-02 15:11 ` Joel Fernandes [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=20191002151116.GA88588@google.com \
--to=joel@joelfernandes.org \
--cc=akiyks@gmail.com \
--cc=boqun.feng@gmail.com \
--cc=dhowells@redhat.com \
--cc=dlustig@nvidia.com \
--cc=j.alglave@ucl.ac.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=luc.maranget@inria.fr \
--cc=npiggin@gmail.com \
--cc=parri.andrea@gmail.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=stern@rowland.harvard.edu \
--cc=will@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 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.