lkml.org 
[lkml]   [2018]   [Jan]   [24]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
Patch in this message
/
From
Subject[Patch] vmbus: Simply hv_get_next_write_location() function
Date
From: Tianyu Lan <Tianyu.Lan@microsoft.com>

The "next" variable is redundant in hv_get_next_write_location().
This patch is to remove it and return write_index directly.

Signed-off-by: Tianyu Lan <Tianyu.Lan@microsoft.com>
---
drivers/hv/ring_buffer.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)

diff --git a/drivers/hv/ring_buffer.c b/drivers/hv/ring_buffer.c
index 12eb8ca..71558e7 100644
--- a/drivers/hv/ring_buffer.c
+++ b/drivers/hv/ring_buffer.c
@@ -82,9 +82,7 @@ static void hv_signal_on_write(u32 old_write, struct vmbus_channel *channel)
static inline u32
hv_get_next_write_location(struct hv_ring_buffer_info *ring_info)
{
- u32 next = ring_info->ring_buffer->write_index;
-
- return next;
+ return ring_info->ring_buffer->write_index;
}

/* Set the next write location for the specified ring buffer. */
--
2.7.4
\
 
 \ /
  Last update: 2018-01-24 07:22    [W:0.448 / U:0.140 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site