Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.kernel > #1460834 > unrolled thread

[PATCH memory-barriers.txt 1/4] memory-barriers.txt: Maintain consistent blank line

Started by"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
First post2016-08-12 00:30 +0200
Last post2016-08-12 10:30 +0200
Articles 6 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  [PATCH memory-barriers.txt 1/4] memory-barriers.txt: Maintain consistent blank line "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> - 2016-08-12 00:30 +0200
    [PATCH memory-barriers.txt 2/4] memory-barriers.txt: Fix wrong section reference "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> - 2016-08-12 00:30 +0200
      [tip:locking/core] locking/Documentation: Fix wrong section  reference tip-bot for SeongJae Park <tipbot@zytor.com> - 2016-08-12 10:30 +0200
    [PATCH memory-barriers.txt 3/4] Doc/memory-barriers: Fix a typo of example result "Paul E. McKenney" <paulmck@linux.vnet.ibm.com> - 2016-08-12 00:30 +0200
      [tip:locking/core] locking/Documentation: Fix a typo of example  result tip-bot for SeongJae Park <tipbot@zytor.com> - 2016-08-12 10:30 +0200
    [tip:locking/core] locking/Documentation: Maintain consistent blank  line tip-bot for SeongJae Park <tipbot@zytor.com> - 2016-08-12 10:30 +0200

#1460834 — [PATCH memory-barriers.txt 1/4] memory-barriers.txt: Maintain consistent blank line

From"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Date2016-08-12 00:30 +0200
Subject[PATCH memory-barriers.txt 1/4] memory-barriers.txt: Maintain consistent blank line
Message-ID<s56E9-1t7-1@gated-at.bofh.it>
From: SeongJae Park <sj38.park@gmail.com>

Signed-off-by: SeongJae Park <sj38.park@gmail.com>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
---
 Documentation/memory-barriers.txt | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Documentation/memory-barriers.txt b/Documentation/memory-barriers.txt
index a4d0a99de04d..e1926a096818 100644
--- a/Documentation/memory-barriers.txt
+++ b/Documentation/memory-barriers.txt
@@ -1928,6 +1928,7 @@ There are some more advanced barrier functions:
 
      See Documentation/DMA-API.txt for more information on consistent memory.
 
+
 MMIO WRITE BARRIER
 ------------------
 
-- 
2.5.2

[toc] | [next] | [standalone]

#1460835 — [PATCH memory-barriers.txt 2/4] memory-barriers.txt: Fix wrong section reference

From"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Date2016-08-12 00:30 +0200
Subject[PATCH memory-barriers.txt 2/4] memory-barriers.txt: Fix wrong section reference
Message-ID<s56Ea-1t7-9@gated-at.bofh.it>
In reply to#1460834
From: SeongJae Park <sj38.park@gmail.com>

Signed-off-by: SeongJae Park <sj38.park@gmail.com>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
---
 Documentation/memory-barriers.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/memory-barriers.txt b/Documentation/memory-barriers.txt
index e1926a096818..19c8eb6f246e 100644
--- a/Documentation/memory-barriers.txt
+++ b/Documentation/memory-barriers.txt
@@ -2076,7 +2076,7 @@ systems, and so cannot be counted on in such a situation to actually achieve
 anything at all - especially with respect to I/O accesses - unless combined
 with interrupt disabling operations.
 
-See also the section on "Inter-CPU locking barrier effects".
+See also the section on "Inter-CPU acquiring barrier effects".
 
 
 As an example, consider the following:
-- 
2.5.2

[toc] | [prev] | [next] | [standalone]

#1461002 — [tip:locking/core] locking/Documentation: Fix wrong section reference

Fromtip-bot for SeongJae Park <tipbot@zytor.com>
Date2016-08-12 10:30 +0200
Subject[tip:locking/core] locking/Documentation: Fix wrong section reference
Message-ID<s5g0N-7Fi-5@gated-at.bofh.it>
In reply to#1460835
Commit-ID:  d7cab36db83be458e8987ae352902958977e7925
Gitweb:     http://git.kernel.org/tip/d7cab36db83be458e8987ae352902958977e7925
Author:     SeongJae Park <sj38.park@gmail.com>
AuthorDate: Thu, 11 Aug 2016 11:17:41 -0700
Committer:  Ingo Molnar <mingo@kernel.org>
CommitDate: Fri, 12 Aug 2016 08:24:13 +0200

locking/Documentation: Fix wrong section reference

Signed-off-by: SeongJae Park <sj38.park@gmail.com>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: dhowells@redhat.com
Cc: linux-arch@vger.kernel.org
Cc: will.deacon@arm.com
Link: http://lkml.kernel.org/r/1470939463-31950-2-git-send-email-paulmck@linux.vnet.ibm.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
 Documentation/memory-barriers.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/memory-barriers.txt b/Documentation/memory-barriers.txt
index e1926a0..19c8eb6 100644
--- a/Documentation/memory-barriers.txt
+++ b/Documentation/memory-barriers.txt
@@ -2076,7 +2076,7 @@ systems, and so cannot be counted on in such a situation to actually achieve
 anything at all - especially with respect to I/O accesses - unless combined
 with interrupt disabling operations.
 
-See also the section on "Inter-CPU locking barrier effects".
+See also the section on "Inter-CPU acquiring barrier effects".
 
 
 As an example, consider the following:

[toc] | [prev] | [next] | [standalone]

#1460839 — [PATCH memory-barriers.txt 3/4] Doc/memory-barriers: Fix a typo of example result

From"Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
Date2016-08-12 00:30 +0200
Subject[PATCH memory-barriers.txt 3/4] Doc/memory-barriers: Fix a typo of example result
Message-ID<s56Ea-1t7-15@gated-at.bofh.it>
In reply to#1460834
From: SeongJae Park <sj38.park@gmail.com>

An example result for data dependent write has a typo.  This commit
fixes the wrong typo.

Signed-off-by: SeongJae Park <sj38.park@gmail.com>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
---
 Documentation/memory-barriers.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/memory-barriers.txt b/Documentation/memory-barriers.txt
index 19c8eb6f246e..ba818ecce6f9 100644
--- a/Documentation/memory-barriers.txt
+++ b/Documentation/memory-barriers.txt
@@ -609,7 +609,7 @@ A data-dependency barrier must also order against dependent writes:
 The data-dependency barrier must order the read into Q with the store
 into *Q.  This prohibits this outcome:
 
-	(Q == B) && (B == 4)
+	(Q == &B) && (B == 4)
 
 Please note that this pattern should be rare.  After all, the whole point
 of dependency ordering is to -prevent- writes to the data structure, along
-- 
2.5.2

[toc] | [prev] | [next] | [standalone]

#1461003 — [tip:locking/core] locking/Documentation: Fix a typo of example result

Fromtip-bot for SeongJae Park <tipbot@zytor.com>
Date2016-08-12 10:30 +0200
Subject[tip:locking/core] locking/Documentation: Fix a typo of example result
Message-ID<s5g0N-7Fi-15@gated-at.bofh.it>
In reply to#1460839
Commit-ID:  8b9e771555745a029557a0a481e760fb84376a35
Gitweb:     http://git.kernel.org/tip/8b9e771555745a029557a0a481e760fb84376a35
Author:     SeongJae Park <sj38.park@gmail.com>
AuthorDate: Thu, 11 Aug 2016 11:17:42 -0700
Committer:  Ingo Molnar <mingo@kernel.org>
CommitDate: Fri, 12 Aug 2016 08:24:13 +0200

locking/Documentation: Fix a typo of example result

An example result for data dependent write has a typo.  This commit
fixes the wrong typo.

Signed-off-by: SeongJae Park <sj38.park@gmail.com>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: dhowells@redhat.com
Cc: linux-arch@vger.kernel.org
Cc: will.deacon@arm.com
Link: http://lkml.kernel.org/r/1470939463-31950-3-git-send-email-paulmck@linux.vnet.ibm.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
 Documentation/memory-barriers.txt | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Documentation/memory-barriers.txt b/Documentation/memory-barriers.txt
index 19c8eb6..ba818ec 100644
--- a/Documentation/memory-barriers.txt
+++ b/Documentation/memory-barriers.txt
@@ -609,7 +609,7 @@ A data-dependency barrier must also order against dependent writes:
 The data-dependency barrier must order the read into Q with the store
 into *Q.  This prohibits this outcome:
 
-	(Q == B) && (B == 4)
+	(Q == &B) && (B == 4)
 
 Please note that this pattern should be rare.  After all, the whole point
 of dependency ordering is to -prevent- writes to the data structure, along

[toc] | [prev] | [next] | [standalone]

#1461001 — [tip:locking/core] locking/Documentation: Maintain consistent blank line

Fromtip-bot for SeongJae Park <tipbot@zytor.com>
Date2016-08-12 10:30 +0200
Subject[tip:locking/core] locking/Documentation: Maintain consistent blank line
Message-ID<s5g0N-7Fi-7@gated-at.bofh.it>
In reply to#1460834
Commit-ID:  dfeccea61716d3ca1bf3477610d1f29abf6d99ca
Gitweb:     http://git.kernel.org/tip/dfeccea61716d3ca1bf3477610d1f29abf6d99ca
Author:     SeongJae Park <sj38.park@gmail.com>
AuthorDate: Thu, 11 Aug 2016 11:17:40 -0700
Committer:  Ingo Molnar <mingo@kernel.org>
CommitDate: Fri, 12 Aug 2016 08:24:13 +0200

locking/Documentation: Maintain consistent blank line

Signed-off-by: SeongJae Park <sj38.park@gmail.com>
Signed-off-by: Paul E. McKenney <paulmck@linux.vnet.ibm.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Peter Zijlstra <peterz@infradead.org>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: dhowells@redhat.com
Cc: linux-arch@vger.kernel.org
Cc: will.deacon@arm.com
Link: http://lkml.kernel.org/r/1470939463-31950-1-git-send-email-paulmck@linux.vnet.ibm.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
---
 Documentation/memory-barriers.txt | 1 +
 1 file changed, 1 insertion(+)

diff --git a/Documentation/memory-barriers.txt b/Documentation/memory-barriers.txt
index a4d0a99..e1926a0 100644
--- a/Documentation/memory-barriers.txt
+++ b/Documentation/memory-barriers.txt
@@ -1928,6 +1928,7 @@ There are some more advanced barrier functions:
 
      See Documentation/DMA-API.txt for more information on consistent memory.
 
+
 MMIO WRITE BARRIER
 ------------------

[toc] | [prev] | [standalone]

Back to top | Article view | linux.kernel

csiph-web