From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Andrea Parri <parri.andrea@gmail.com>
Cc: Boqun Feng <boqun.feng@gmail.com>,
Alan Stern <stern@rowland.harvard.edu>,
Peter Zijlstra <peterz@infradead.org>,
will.deacon@arm.com, npiggin@gmail.com, dhowells@redhat.com,
j.alglave@ucl.ac.uk, luc.maranget@inria.fr,
linux-kernel@vger.kernel.org, elena.reshetova@intel.com
Subject: Re: Prototype patch for Linux-kernel memory model
Date: Mon, 20 Nov 2017 11:30:19 -0800 [thread overview]
Message-ID: <20171120193019.GX3624@linux.vnet.ibm.com> (raw)
In-Reply-To: <20171120163343.GA5842@andrea>
On Mon, Nov 20, 2017 at 05:35:04PM +0100, Andrea Parri wrote:
> On Fri, Nov 17, 2017 at 07:27:46PM +0800, Boqun Feng wrote:
> > On Wed, Nov 15, 2017 at 08:37:49AM -0800, Paul E. McKenney wrote:
> > > On Tue, Nov 14, 2017 at 09:15:05AM -0800, Paul E. McKenney wrote:
> > > > On Tue, Nov 14, 2017 at 10:19:21AM -0500, Alan Stern wrote:
[ . . . ]
> > > > I could add a paragraph just before the Signed-off-by/Acked-by/etc.
> > > > block describing the roles and contributions, convert the people who
> > > > were directly involved to Reviewed-by and everyone else to Acked-by
> > > > (unless they explicitly provided a Reviewed-by).
> > > >
> > > > Would that work, or does someone have a better approach?
> > >
> >
> > How about using the shiny new "Co-Developed-by"?
> >
> > https://marc.info/?l=linux-kernel&m=151083859723653&w=2
>
> This seems to be exactly what we were looking for/we needed. Altought
> still undocumented in "mainline", the tag has already found some uses
> in the past, and it appears in its commit log. I've just modified com-
> mit-log.txt in the "memory-model" repo. to adopt this tag.
>
>
> >
> > Besides, as you know, I've been following and learning a lot from this
> > model from maybe very beginning, and I have read throught the documents
> > and cat files, and even got a chance to verify some RCU-involved code
> > with Andrea using this model ;-) So feel free to add:
> >
> > Reviewed-by: Boqun Feng <boqun.feng@gmail.com>
>
> Added. Thanks,
Thank you, Andrea!
I redid the ordering, given that Boqun did not review before we developed,
and also removed his now-redundant Acked-by.
Thanx, Paul
next prev parent reply other threads:[~2017-11-20 19:30 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-13 18:40 Prototype patch for Linux-kernel memory model Paul E. McKenney
2017-11-13 20:09 ` Alan Stern
2017-11-14 4:52 ` Paul E. McKenney
2017-11-14 7:59 ` Peter Zijlstra
2017-11-14 15:19 ` Alan Stern
2017-11-14 17:15 ` Paul E. McKenney
2017-11-15 16:37 ` Paul E. McKenney
2017-11-17 11:27 ` Boqun Feng
2017-11-20 16:35 ` Andrea Parri
2017-11-20 19:30 ` Paul E. McKenney [this message]
2017-12-19 8:36 ` afzal mohammed
2017-12-19 16:05 ` Alan Stern
2017-12-20 11:31 ` afzal mohammed
2017-12-20 16:45 ` Paul E. McKenney
2017-12-21 3:30 ` afzal mohammed
2017-12-21 16:15 ` Paul E. McKenney
2017-12-22 4:11 ` afzal mohammed
2017-12-23 6:14 ` afzal mohammed
2018-01-02 20:25 ` Paul E. McKenney
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=20171120193019.GX3624@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=boqun.feng@gmail.com \
--cc=dhowells@redhat.com \
--cc=elena.reshetova@intel.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=peterz@infradead.org \
--cc=stern@rowland.harvard.edu \
--cc=will.deacon@arm.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 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.