On Fri, 23 Jun 2017 13:45:29 -0700
"Paul E. McKenney" wrote:
> On Fri, Jun 23, 2017 at 01:31:39PM -0700, Palmer Dabbelt wrote:
> > I was reading the memory barries documentation in order to make sure the
> > RISC-V barries were correct, and I found a broken link to the atomic
> > operations docum
On Fri, Jun 23, 2017 at 01:31:39PM -0700, Palmer Dabbelt wrote:
> I was reading the memory barries documentation in order to make sure the
> RISC-V barries were correct, and I found a broken link to the atomic
> operations documentation.
>
> Signed-off-by: Palmer Dabbelt
> Acked-by: Will Deacon
On Fri, 23 Jun 2017 13:29:54 PDT (-0700), cor...@lwn.net wrote:
> On Fri, 23 Jun 2017 13:25:22 -0700
> Palmer Dabbelt wrote:
>
>> I was reading the memory barries documentation in order to make sure the
>> RISC-V barries were correct, and I found a broken link to the atomic
>> operations documenta
I was reading the memory barries documentation in order to make sure the
RISC-V barries were correct, and I found a broken link to the atomic
operations documentation.
Signed-off-by: Palmer Dabbelt
Acked-by: Will Deacon
---
Documentation/memory-barriers.txt | 10 +-
1 file changed, 5 in
On Fri, 23 Jun 2017 13:25:22 -0700
Palmer Dabbelt wrote:
> I was reading the memory barries documentation in order to make sure the
> RISC-V barries were correct, and I found a broken link to the atomic
> operations documentation.
This looks good to me, but can you resend with Paul McKenney on t
I was reading the memory barries documentation in order to make sure the
RISC-V barries were correct, and I found a broken link to the atomic
operations documentation.
Signed-off-by: Palmer Dabbelt
Acked-by: Will Deacon
---
Documentation/memory-barriers.txt | 10 +-
1 file changed, 5 in
