public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: YU Bo <tsu.yubo@gmail.com>
To: Patard <arnaud.patard@rtp-net.org>,
	Kroah-Hartman <gregkh@linuxfoundation.org>,
	yuzibode@126.com, BO <tsu.yubo@gmail.com>
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH] Staging: xgifb: vgatypes.h: Coding style warning fix for block comments
Date: Fri, 15 Jan 2016 17:30:02 +0800	[thread overview]
Message-ID: <20160115092958.GA9097@debian> (raw)

This patch is to vgatypes.h file that fixes up following warnings
reported by checkpatch.pl tool

Signed-off-by: YU Bo <tsu.yubo@gmail.com>
---
  drivers/staging/xgifb/vgatypes.h |   12 ++++++++----
  1 file changed, 8 insertions(+), 4 deletions(-)

diff --git a/drivers/staging/xgifb/vgatypes.h b/drivers/staging/xgifb/vgatypes.h
index 61fa10f..80440f0 100644
--- a/drivers/staging/xgifb/vgatypes.h
+++ b/drivers/staging/xgifb/vgatypes.h
@@ -26,15 +26,19 @@ struct xgi_hw_device_info {
  	void __iomem *pjVideoMemoryAddress;/* base virtual memory address */
  					    /* of Linear VGA memory */

-	unsigned long ulVideoMemorySize; /* size, in bytes, of the
-					    memory on the board */
+	unsigned long ulVideoMemorySize; /*
+					  *  size, in bytes, of the
+					  *  memory on the board
+					  */

  	unsigned char jChipType; /* Used to Identify Graphics Chip */
  				 /* defined in the data structure type  */
  				 /* "XGI_CHIP_TYPE" */

-	unsigned char jChipRevision; /* Used to Identify Graphics
-					Chip Revision */
+	unsigned char jChipRevision; /*
+				      *	Used to Identify Graphics
+				      *	Chip Revision
+				      */

  	unsigned char ujVBChipID; /* the ID of video bridge */
  				  /* defined in the data structure type */
--
1.7.10.4


--
Best Regards

             reply	other threads:[~2016-01-15  1:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-15  9:30 YU Bo [this message]
2016-02-08  4:14 ` [PATCH] Staging: xgifb: vgatypes.h: Coding style warning fix for block comments Kroah-Hartman
2016-02-15 12:18   ` Bo YU

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=20160115092958.GA9097@debian \
    --to=tsu.yubo@gmail.com \
    --cc=arnaud.patard@rtp-net.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yuzibode@126.com \
    /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