[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YshC8sJ4dZq3m2wy@rowland.harvard.edu>
Date: Fri, 8 Jul 2022 10:45:06 -0400
From: Alan Stern <stern@...land.harvard.edu>
To: Marco Elver <elver@...gle.com>
Cc: Paul Heidekrüger <paul.heidekrueger@...tum.de>,
Andrea Parri <parri.andrea@...il.com>,
Will Deacon <will@...nel.org>,
Peter Zijlstra <peterz@...radead.org>,
Boqun Feng <boqun.feng@...il.com>,
Nicholas Piggin <npiggin@...il.com>,
David Howells <dhowells@...hat.com>,
Jade Alglave <j.alglave@....ac.uk>,
Luc Maranget <luc.maranget@...ia.fr>,
"Paul E. McKenney" <paulmck@...nel.org>,
Akira Yokosawa <akiyks@...il.com>,
Daniel Lustig <dlustig@...dia.com>,
Joel Fernandes <joel@...lfernandes.org>,
linux-kernel@...r.kernel.org, linux-arch@...r.kernel.org,
Charalampos Mainas <charalampos.mainas@...il.com>,
Pramod Bhatotia <pramod.bhatotia@...tum.de>,
Soham Chakraborty <s.s.chakraborty@...elft.nl>,
Martin Fink <martin.fink@...tum.de>
Subject: Re: [PATCH v2] tools/memory-model: Clarify LKMM's limitations in
litmus-tests.txt
On Fri, Jul 08, 2022 at 01:44:06PM +0200, Marco Elver wrote:
> On Tue, 14 Jun 2022 at 17:49, Paul Heidekrüger
> <paul.heidekrueger@...tum.de> wrote:
> >
> > As discussed, clarify LKMM not recognizing certain kinds of orderings.
> > In particular, highlight the fact that LKMM might deliberately make
> > weaker guarantees than compilers and architectures.
> >
> > Link: https://lore.kernel.org/all/YpoW1deb%2FQeeszO1@ethstick13.dse.in.tum.de/T/#u
> > Signed-off-by: Paul Heidekrüger <paul.heidekrueger@...tum.de>
> > Co-developed-by: Alan Stern <stern@...land.harvard.edu>
>
> Reviewed-by: Marco Elver <elver@...gle.com>
>
> However with the Co-developed-by, this is missing Alan's SOB.
For the record:
Signed-off-by: Alan Stern <stern@...land.harvard.edu>
(Note that according to Documentation/process/submitting-patches.rst,
the submitting author's SOB is supposed to come last.)
Alan
Powered by blists - more mailing lists