public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vikram Dhillon <opensolarisdev@gmail.com>
To: gregkh@suse.de
Cc: wfp5p@virginia.edu, npalix@diku.dk, devel@driverdev.osuosl.org,
	linux-kernel@vger.kernel.org,
	Vikram Dhillon <opensolarisdev@gmail.com>
Subject: [PATCH 3/3] Staging: hv: NetVsc.c: Fixed a spacing issue
Date: Sat, 20 Mar 2010 02:07:28 -0400	[thread overview]
Message-ID: <1269065248-10575-1-git-send-email-opensolarisdev@gmail.com> (raw)

Fixed spacing issues in 2 pointers.

Signed-off-by: Vikram Dhillon <opensolarisdev@gmail.com>

---
 drivers/staging/hv/NetVsc.c |    4 ++--
 1 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/staging/hv/NetVsc.c b/drivers/staging/hv/NetVsc.c
index 1c717f9..e57b70f 100644
--- a/drivers/staging/hv/NetVsc.c
+++ b/drivers/staging/hv/NetVsc.c
@@ -1086,7 +1086,7 @@ static void NetVscOnReceive(struct hv_device *Device,
 	}
 
 	/* Remove the 1st packet to represent the xfer page packet itself */
-	xferpagePacket = (struct xferpage_packet*)listHead.next;
+	xferpagePacket = (struct xferpage_packet *)listHead.next;
 	list_del(&xferpagePacket->ListEntry);
 
 	/* This is how much we can satisfy */
@@ -1102,7 +1102,7 @@ static void NetVscOnReceive(struct hv_device *Device,
 
 	/* Each range represents 1 RNDIS pkt that contains 1 ethernet frame */
 	for (i = 0; i < (count - 1); i++) {
-		netvscPacket = (struct hv_netvsc_packet*)listHead.next;
+		netvscPacket = (struct hv_netvsc_packet *)listHead.next;
 		list_del(&netvscPacket->ListEntry);
 
 		/* Initialize the netvsc packet */
-- 
1.6.3.3


             reply	other threads:[~2010-03-20  6:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-20  6:07 Vikram Dhillon [this message]
2010-04-27 21:44 ` [PATCH 3/3] Staging: hv: NetVsc.c: Fixed a spacing issue Greg KH

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1269065248-10575-1-git-send-email-opensolarisdev@gmail.com \
    --to=opensolarisdev@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=npalix@diku.dk \
    --cc=wfp5p@virginia.edu \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox