mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alan Stern <stern@rowland.harvard.edu>
To: "Paul Heidekrüger" <paul.heidekrueger@in.tum.de>
Cc: "Andrea Parri" <parri.andrea@gmail.com>,
	"Will Deacon" <will@kernel.org>,
	"Peter Zijlstra" <peterz@infradead.org>,
	"Boqun Feng" <boqun.feng@gmail.com>,
	"Nicholas Piggin" <npiggin@gmail.com>,
	"David Howells" <dhowells@redhat.com>,
	"Jade Alglave" <j.alglave@ucl.ac.uk>,
	"Luc Maranget" <luc.maranget@inria.fr>,
	"Paul E. McKenney" <paulmck@kernel.org>,
	"Akira Yokosawa" <akiyks@gmail.com>,
	"Daniel Lustig" <dlustig@nvidia.com>,
	"Joel Fernandes" <joel@joelfernandes.org>,
	"Björn Töpel" <bjorn@kernel.org>,
	linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org,
	"Marco Elver" <elver@google.com>,
	"Charalampos Mainas" <charalampos.mainas@gmail.com>,
	"Pramod Bhatotia" <pramod.bhatotia@in.tum.de>
Subject: Re: [PATCH] tools/memory-model: Clarify syntactic and semantic dependencies
Date: Thu, 27 Jan 2022 12:04:26 -0500	[thread overview]
Message-ID: <YfLQmgsXp6pg0XIy@rowland.harvard.edu> (raw)
In-Reply-To: <YfJ7Rr9Kdk4u78lt@Pauls-MacBook-Pro.local>

On Thu, Jan 27, 2022 at 12:00:22PM +0100, Paul Heidekrüger wrote:
> On Tue, Jan 25, 2022 at 04:00:11PM -0500, Alan Stern wrote:
> > That's a very abstract way of describing the situation; it doesn't do a 
> > good job of getting the real idea across.  It also mixes up two separate 
> > ideas: behaviors being unaffected by a syntactic dependency and 
> > behaviors being undefined.  They should be described separately. 
> 
> Many thanks for the feedback! I agree, the explanation works a lot
> better once readers have been introduced to data, addr and ctrl
> relations. 
> 
> > I would prefer something along these lines...
> 
> Shall I resubmit the patch with you as co-developer, or, given that it's
> arguably your work now, would you like to submit the patch yourself?

I'll submit it myself, with Suggested-by: you.  How does that sound?

Alan

  reply	other threads:[~2022-01-27 17:04 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-25 17:28 Paul Heidekrüger
2022-01-25 21:00 ` Alan Stern
2022-01-27 11:00   ` Paul Heidekrüger
2022-01-27 17:04     ` Alan Stern [this message]
2022-01-27 20:49       ` Paul Heidekrüger
2022-01-27 21:11         ` [PATCH] tools/memory-model: Explain " Alan Stern
2022-02-01  1:42           ` Akira Yokosawa
2022-02-01 18:02           ` Paul E. McKenney
2022-02-01 18:53             ` Alan Stern
2022-02-01 19:02               ` Paul E. McKenney
2022-02-01 19:00           ` [PATCH v2] " Alan Stern
2022-02-01 19:09             ` 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=YfLQmgsXp6pg0XIy@rowland.harvard.edu \
    --to=stern@rowland.harvard.edu \
    --cc=akiyks@gmail.com \
    --cc=bjorn@kernel.org \
    --cc=boqun.feng@gmail.com \
    --cc=charalampos.mainas@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=dlustig@nvidia.com \
    --cc=elver@google.com \
    --cc=j.alglave@ucl.ac.uk \
    --cc=joel@joelfernandes.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luc.maranget@inria.fr \
    --cc=npiggin@gmail.com \
    --cc=parri.andrea@gmail.com \
    --cc=paul.heidekrueger@in.tum.de \
    --cc=paulmck@kernel.org \
    --cc=peterz@infradead.org \
    --cc=pramod.bhatotia@in.tum.de \
    --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 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®