[PATCH 108/206] Staging: hv: Cleanup ring_buffer.h

From: K. Y. Srinivasan
Date: Mon May 09 2011 - 17:49:28 EST


Access to these variables is already serialized via a spin lock. Get
rid of the unnecessary volatile qualifier.

Signed-off-by: K. Y. Srinivasan <kys@xxxxxxxxxxxxx>
Signed-off-by: Haiyang Zhang <haiyangz@xxxxxxxxxxxxx>
Signed-off-by: Abhishek Kane <v-abkane@xxxxxxxxxxxxx>
Signed-off-by: Hank Janssen <hjanssen@xxxxxxxxxxxxx>
---
drivers/staging/hv/ring_buffer.h | 7 +++----
1 files changed, 3 insertions(+), 4 deletions(-)

diff --git a/drivers/staging/hv/ring_buffer.h b/drivers/staging/hv/ring_buffer.h
index 1bc0b8a..089c536 100644
--- a/drivers/staging/hv/ring_buffer.h
+++ b/drivers/staging/hv/ring_buffer.h
@@ -30,12 +30,12 @@

struct hv_ring_buffer {
/* Offset in bytes from the start of ring data below */
- volatile u32 write_index;
+ u32 write_index;

/* Offset in bytes from the start of ring data below */
- volatile u32 read_index;
+ u32 read_index;

- volatile u32 interrupt_mask;
+ u32 interrupt_mask;

/* Pad it to PAGE_SIZE so that data starts on page boundary */
u8 reserved[4084];
@@ -45,7 +45,6 @@ struct hv_ring_buffer {
* vmbus connection also uses this data structure and its data starts
* here, we commented out this field.
*/
- /* volatile u32 InterruptMask; */

/*
* Ring data starts here + RingDataStartOffset
--
1.7.4.1

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/