[RFC PATCH v2 0/2] CodeSamples: Cleanups and fixes

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



>From 489b5e3bdeba2f9b733dbe3d85390368dd159174 Mon Sep 17 00:00:00 2001
From: Akira Yokosawa <akiyks@xxxxxxxxx>
Date: Tue, 30 May 2017 20:44:52 +0900
Subject: [RFC PATCH v2 0/2] CodeSamples: Cleanups and fixes

Hi Paul,

This is the respin of the latter two patches of v1. I'm keeping RFC
because of some questions.

"long" -> "intptr_t" changes in Patch 1 have no effect on a platform
where "long" and "intptr_t" have the same width, but I think they
are good in portability POV.

WRITE_ONCE() in Patch 2 is placed under the assignment to the array
because I could not translate post increment in any other way.
Does the WRITE_ONCE() ensure the outer "while" capture the value?

              Thanks, Akira
-- 
Akira Yokosawa (2):
  CodeSamples: Use 'intptr_t' to be compatible with 'void *'
  CodeSamples/defer: Add compiler barriers in gettimestampmp.c

 CodeSamples/SMPdesign/matmul.c     | 4 ++--
 CodeSamples/SMPdesign/smpalloc.c   | 4 ++--
 CodeSamples/defer/gettimestampmp.c | 7 ++++---
 CodeSamples/intro/threadcreate.c   | 4 ++--
 4 files changed, 10 insertions(+), 9 deletions(-)

-- 
2.7.4


--
To unsubscribe from this list: send the line "unsubscribe perfbook" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Linux NFS]     [Linux NILFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux