From: Guangbin Huang <huangguangbin2@huawei.com>
To: <davem@davemloft.net>, <kuba@kernel.org>, <xie.he.0141@gmail.com>,
<ms@dev.tdt.de>, <willemb@google.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<lipeng321@huawei.com>, <tanhuazhong@huawei.com>,
<huangguangbin2@huawei.com>
Subject: [PATCH net-next 01/10] net: sealevel: remove redundant blank lines
Date: Sun, 30 May 2021 14:24:25 +0800 [thread overview]
Message-ID: <1622355874-18933-2-git-send-email-huangguangbin2@huawei.com> (raw)
In-Reply-To: <1622355874-18933-1-git-send-email-huangguangbin2@huawei.com>
From: Peng Li <lipeng321@huawei.com>
This patch removes some redundant blank lines.
Signed-off-by: Peng Li <lipeng321@huawei.com>
Signed-off-by: Guangbin Huang <huangguangbin2@huawei.com>
---
drivers/net/wan/sealevel.c | 5 -----
1 file changed, 5 deletions(-)
diff --git a/drivers/net/wan/sealevel.c b/drivers/net/wan/sealevel.c
index 7dddc9dcbe23..62cc59892d1e 100644
--- a/drivers/net/wan/sealevel.c
+++ b/drivers/net/wan/sealevel.c
@@ -29,14 +29,12 @@
#include <asm/byteorder.h>
#include "z85230.h"
-
struct slvl_device
{
struct z8530_channel *chan;
int channel;
};
-
struct slvl_board
{
struct slvl_device dev[2];
@@ -195,7 +193,6 @@ static int slvl_setup(struct slvl_device *sv, int iobase, int irq)
return 0;
}
-
/*
* Allocate and setup Sealevel board.
*/
@@ -256,7 +253,6 @@ static __init struct slvl_board *slvl_init(int iobase, int irq,
outb(3 | (1 << 7), b->iobase + 4);
-
/* We want a fast IRQ for this device. Actually we'd like an even faster
IRQ ;) - This is one driver RtLinux is made for */
@@ -351,7 +347,6 @@ static void __exit slvl_shutdown(struct slvl_board *b)
kfree(b);
}
-
static int io=0x238;
static int txdma=1;
static int rxdma=3;
--
2.8.1
next prev parent reply other threads:[~2021-05-30 6:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-30 6:24 [PATCH net-next 00/10] net: sealevel: clean up some code style issues Guangbin Huang
2021-05-30 6:24 ` Guangbin Huang [this message]
2021-05-30 6:24 ` [PATCH net-next 02/10] net: sealevel: add blank line after declarations Guangbin Huang
2021-05-30 6:24 ` [PATCH net-next 03/10] net: sealevel: fix the code style issue about "foo* bar" Guangbin Huang
2021-05-30 6:24 ` [PATCH net-next 04/10] net: sealevel: open brace '{' following struct go on the same line Guangbin Huang
2021-05-30 6:24 ` [PATCH net-next 05/10] net: sealevel: add some required spaces Guangbin Huang
2021-05-30 6:24 ` [PATCH net-next 06/10] net: sealevel: remove redundant initialization for statics Guangbin Huang
2021-05-30 6:24 ` [PATCH net-next 07/10] net: sealevel: fix a code style issue about switch and case Guangbin Huang
2021-05-30 6:24 ` [PATCH net-next 08/10] net: sealevel: remove meaningless comments Guangbin Huang
2021-05-30 6:24 ` [PATCH net-next 09/10] net: sealevel: fix the comments style issue Guangbin Huang
2021-05-30 6:24 ` [PATCH net-next 10/10] net: sealevel: fix the alignment issue Guangbin Huang
2021-06-01 5:20 ` [PATCH net-next 00/10] net: sealevel: clean up some code style issues patchwork-bot+netdevbpf
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=1622355874-18933-2-git-send-email-huangguangbin2@huawei.com \
--to=huangguangbin2@huawei.com \
--cc=davem@davemloft.net \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lipeng321@huawei.com \
--cc=ms@dev.tdt.de \
--cc=netdev@vger.kernel.org \
--cc=tanhuazhong@huawei.com \
--cc=willemb@google.com \
--cc=xie.he.0141@gmail.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;
as well as URLs for NNTP newsgroup(s).