From: Payal Kshirsagar <payalskshirsagar1234@gmail.com>
To: manishc@marvell.com, GR-Linux-NIC-Dev@marvell.com,
gregkh@linuxfoundation.org, outreachy-kernel@googlegroups.com
Cc: Payal Kshirsagar <payalskshirsagar1234@gmail.com>
Subject: [PATCH v2 3/3] [Outreachy kernel] staging: qlge: qlge.h: remove excess newlines
Date: Mon, 9 Mar 2020 21:57:28 +0530 [thread overview]
Message-ID: <20200309162728.4342-4-payalskshirsagar1234@gmail.com> (raw)
In-Reply-To: <20200309162728.4342-1-payalskshirsagar1234@gmail.com>
Blank lines aren't necessary after an open brace '{'.
Signed-off-by: Payal Kshirsagar <payalskshirsagar1234@gmail.com>
---
Nothing has changed.
drivers/staging/qlge/qlge.h | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/staging/qlge/qlge.h b/drivers/staging/qlge/qlge.h
index 4ef8dae3d7a0..fc8c5ca8935d 100644
--- a/drivers/staging/qlge/qlge.h
+++ b/drivers/staging/qlge/qlge.h
@@ -119,7 +119,6 @@ enum {
* Processor Address Register (PROC_ADDR) bit definitions.
*/
enum {
-
/* Misc. stuff */
MAILBOX_COUNT = 16,
MAILBOX_TIMEOUT = 5,
@@ -1762,7 +1761,6 @@ struct ql_nic_misc {
};
struct ql_reg_dump {
-
/* segment 0 */
struct mpi_coredump_global_header mpi_global_header;
@@ -2059,7 +2057,6 @@ enum {
};
struct nic_operations {
-
int (*get_flash) (struct ql_adapter *);
int (*port_initialize) (struct ql_adapter *);
};
--
2.17.1
prev parent reply other threads:[~2020-03-09 16:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-09 16:27 [PATCH v2 0/3] [Outreachy kernel] staging: qlge: qlge.h: cleanup suggested by checkpatch Payal Kshirsagar
2020-03-09 16:27 ` [PATCH v2 1/3] [Outreachy kernel] staging: qlge: qlge.h: remove spaces before tabs and align code Payal Kshirsagar
2020-03-09 16:27 ` [PATCH v2 2/3] [Outreachy kernel] staging: qlge: qlge.h: add spaces around operators Payal Kshirsagar
2020-03-09 16:27 ` Payal Kshirsagar [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=20200309162728.4342-4-payalskshirsagar1234@gmail.com \
--to=payalskshirsagar1234@gmail.com \
--cc=GR-Linux-NIC-Dev@marvell.com \
--cc=gregkh@linuxfoundation.org \
--cc=manishc@marvell.com \
--cc=outreachy-kernel@googlegroups.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 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.