All of lore.kernel.org
 help / color / mirror / Atom feed
From: Walt Feasel <waltfeasel@gmail.com>
To: arnaud.patard@rtp-net.org, gregkh@linuxfoundation.org,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Cc: Walt Feasel <waltfeasel@gmail.com>
Subject: [PATCH v2 1/2] staging: xgifb: vb_table.h Blank line after declarations
Date: Tue, 15 Nov 2016 05:36:44 -0500	[thread overview]
Message-ID: <78551bd26972cdc080a4844f6890b7b6b68bdb25.1479205381.git.waltfeasel@gmail.com> (raw)
In-Reply-To: <cover.1479205381.git.waltfeasel@gmail.com>
In-Reply-To: <cover.1479205381.git.waltfeasel@gmail.com>

Make suggested modification from checkpatch in reference
to: CHECK: Please use a blank line after
function/struct/union/enum declarations

Signed-off-by: Walt Feasel <waltfeasel@gmail.com>
---
v2 corrects mailing format to link patches
and change subject line
 drivers/staging/xgifb/vb_table.h | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/staging/xgifb/vb_table.h b/drivers/staging/xgifb/vb_table.h
index c801deb..f2fabb8 100644
--- a/drivers/staging/xgifb/vb_table.h
+++ b/drivers/staging/xgifb/vb_table.h
@@ -1701,6 +1701,7 @@ static const struct XGI_LVDSCRT1VDataStruct XGI_LVDSCRT11280x1024_1_Vx75[] = {
 	{ {0x28, 0xF5, 0x00, 0x84, 0xFF, 0x29, 0x90} },/* ; 04 (x768) */
 	{ {0x28, 0x5A, 0x13, 0x87, 0xFF, 0x29, 0xA9} } /* ; 05 (x1024) */
 };
+
 /* CR00,CR02,CR03,CR04,CR05,SR0B,SR0C,SR0E */
 static const struct XGI_LVDSCRT1HDataStruct XGI_LVDSCRT11280x1024_2_Hx75[] = {
 	{ {0x7E, 0x3B, 0x9A, 0x44, 0x12, 0x00, 0x01, 0x00} },/* ; 00 (320x) */
-- 
2.1.4

  reply	other threads:[~2016-11-15 10:37 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-15 10:36 [PATCH v2 0/2] Style edits for xgifb: vb_table.h Walt Feasel
2016-11-15 10:36 ` Walt Feasel [this message]
2016-11-15 10:36 ` [PATCH v2 2/2] staging: xgifb: vb_table.h Preferred space around Walt Feasel

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=78551bd26972cdc080a4844f6890b7b6b68bdb25.1479205381.git.waltfeasel@gmail.com \
    --to=waltfeasel@gmail.com \
    --cc=arnaud.patard@rtp-net.org \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.