All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@kernel.org>
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org, sj38.park@gmail.com,
	josh@joshtriplett.org, rostedt@goodmis.org,
	mathieu.desnoyers@efficios.com, jiangshanlai@gmail.com,
	torvalds@linux-foundation.org
Subject: Re: [GIT PULL v2 rcu/next] memory-barriers.txt commits for 4.6
Date: Wed, 16 Mar 2016 08:26:25 +0100	[thread overview]
Message-ID: <20160316072625.GA10500@gmail.com> (raw)
In-Reply-To: <20160315154631.GA1712@linux.vnet.ibm.com>


* Paul E. McKenney <paulmck@linux.vnet.ibm.com> wrote:

> [...] In fact, in view of the no-diagrams and no-quizzes restrictions, I don't 
> see a way to improve on comments in the source code. [...]

So I don't think there's such a hard restriction: AFAICS Linus's main problem was 
the dual .html and .htmlx file for what essentially are the same documents.

If you can solve that with a single (.html?) file then I think it's all OK.

> The memory-barriers.txt commits are available in the git repository at:
> 
>   git://git.kernel.org/pub/scm/linux/kernel/git/paulmck/linux-rcu.git for-mingo
> 
> for you to fetch changes up to 65f95ff2e41a32dd190cf28e3abb029625eef968:
> 
>   documentation: Clarify compiler store-fusion example (2016-03-14 15:52:19 -0700)
> 
> ----------------------------------------------------------------
> Paul E. McKenney (7):
>       documentation: Fix control dependency and identical stores
>       documentation: Fix memory-barriers.txt section references
>       documentation: Remove obsolete reference to RCU-protected indexes
>       documentation: Subsequent writes ordered by rcu_dereference()
>       documentation: Distinguish between local and global transitivity
>       documentation:  Add alternative release-acquire outcome
>       documentation: Transitivity is not cumulativity
> 
> SeongJae Park (1):
>       documentation: Clarify compiler store-fusion example
> 
>  Documentation/memory-barriers.txt | 141 +++++++++++++++++++++++++++++++-------
>  1 file changed, 116 insertions(+), 25 deletions(-)

Pulled into tip:locking/urgent, thanks a lot Paul!

	Ingo

  reply	other threads:[~2016-03-16  7:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-15 15:46 [GIT PULL v2 rcu/next] memory-barriers.txt commits for 4.6 Paul E. McKenney
2016-03-16  7:26 ` Ingo Molnar [this message]
2016-03-16 12:51   ` 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=20160316072625.GA10500@gmail.com \
    --to=mingo@kernel.org \
    --cc=jiangshanlai@gmail.com \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=rostedt@goodmis.org \
    --cc=sj38.park@gmail.com \
    --cc=torvalds@linux-foundation.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.