mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Scott Matheina <scott@matheina.com>
To: linux-kernel@vger.kernel.org
Cc: Forest Bond <forest@alittletooquiet.net>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Rithvik Patibandla <rithvikp98@gmail.com>,
	Alison Schofield <amsfield22@gmail.com>,
	Johannes Berg <johannes.berg@intel.com>,
	Parth Sane <laerdevstudios@gmail.com>,
	Elise Lennion <elise.lennion@gmail.com>,
	Nadim Almas <nadim.902@gmail.com>,
	Wolfram Sang <wsa-dev@sang-engineering.com>,
	Mihaela Muraru <mihaela.muraru21@gmail.com>,
	maomao xu <albert008.xu@gmail.com>,
	devel@driverdev.osuosl.org
Subject: [PATCH 4/4] staging:vt6656:main_usb.c Removed un-needed blank lines
Date: Mon,  9 Jan 2017 22:42:53 -0600	[thread overview]
Message-ID: <1484023383-10471-4-git-send-email-scott@matheina.com> (raw)
In-Reply-To: <1484023383-10471-1-git-send-email-scott@matheina.com>

Fixed the following checkpatch warnings by deleting blank lines
Blank lines aren't necessary before a close brace '}'
Blank lines aren't necessary after an open brace '{'
Please don't use multiple blank lines

Signed-off-by: Scott Matheina <scott@matheina.com>
---
 drivers/staging/vt6656/main_usb.c | 4 ----
 1 file changed, 4 deletions(-)

diff --git a/drivers/staging/vt6656/main_usb.c b/drivers/staging/vt6656/main_usb.c
index d29f097..9e074e9 100644
--- a/drivers/staging/vt6656/main_usb.c
+++ b/drivers/staging/vt6656/main_usb.c
@@ -278,7 +278,6 @@ static int vnt_init_registers(struct vnt_private *priv)
 	if (priv->rf_type == RF_VT3226D0) {
 		if ((priv->eeprom[EEP_OFS_MAJOR_VER] == 0x1) &&
 		    (priv->eeprom[EEP_OFS_MINOR_VER] >= 0x4)) {
-
 			calib_tx_iq = priv->eeprom[EEP_OFS_CALIB_TX_IQ];
 			calib_tx_dc = priv->eeprom[EEP_OFS_CALIB_TX_DC];
 			calib_rx_iq = priv->eeprom[EEP_OFS_CALIB_RX_IQ];
@@ -694,7 +693,6 @@ static void vnt_bss_info_changed(struct ieee80211_hw *hw,
 	if (changed & BSS_CHANGED_BSSID && conf->bssid)
 		vnt_mac_set_bssid_addr(priv, (u8 *)conf->bssid);
 
-
 	if (changed & BSS_CHANGED_BASIC_RATES) {
 		priv->basic_rates = conf->basic_rates;
 
@@ -817,7 +815,6 @@ static void vnt_configure(struct ieee80211_hw *hw,
 		} else {
 			rx_mode &= ~(RCR_MULTICAST | RCR_BROADCAST);
 		}
-
 	}
 
 	if (changed_flags & (FIF_OTHER_BSS | FIF_BCN_PRBRESP_PROMISC)) {
@@ -928,7 +925,6 @@ static const struct ieee80211_ops vnt_mac_ops = {
 
 int vnt_init(struct vnt_private *priv)
 {
-
 	if (!(vnt_init_registers(priv)))
 		return -EAGAIN;
 
-- 
2.7.4

      parent reply	other threads:[~2017-01-10  4:43 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-10  4:42 [PATCH 1/4] staging:vt6656:key.c Aligned code with open parenthesis Scott Matheina
2017-01-10  4:42 ` [PATCH 2/4] staging:vt6656:mac.c Aligned code to match " Scott Matheina
2017-01-10  4:42 ` [PATCH 3/4] staging:vt6656:main_usb.c " Scott Matheina
2017-01-10  4:42 ` Scott Matheina [this message]

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=1484023383-10471-4-git-send-email-scott@matheina.com \
    --to=scott@matheina.com \
    --cc=albert008.xu@gmail.com \
    --cc=amsfield22@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=elise.lennion@gmail.com \
    --cc=forest@alittletooquiet.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=johannes.berg@intel.com \
    --cc=laerdevstudios@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mihaela.muraru21@gmail.com \
    --cc=nadim.902@gmail.com \
    --cc=rithvikp98@gmail.com \
    --cc=wsa-dev@sang-engineering.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

all inboxes | Powered by JetHome®