From: Peng Li <lipeng321@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>,
<huangguangbin2@huawei.com>
Subject: [PATCH net-next 6/6] net: pci200syn: fix the comments style issue
Date: Tue, 15 Jun 2021 21:54:23 +0800 [thread overview]
Message-ID: <1623765263-36775-7-git-send-email-lipeng321@huawei.com> (raw)
In-Reply-To: <1623765263-36775-1-git-send-email-lipeng321@huawei.com>
Networking block comments don't use an empty /* line,
use /* Comment...
This patch fixes the comments style issues.
Signed-off-by: Peng Li <lipeng321@huawei.com>
---
drivers/net/wan/pci200syn.c | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/drivers/net/wan/pci200syn.c b/drivers/net/wan/pci200syn.c
index abca13b..dee9c4e 100644
--- a/drivers/net/wan/pci200syn.c
+++ b/drivers/net/wan/pci200syn.c
@@ -42,8 +42,7 @@
static int pci_clock_freq = 33000000;
#define CLOCK_BASE pci_clock_freq
-/*
- * PLX PCI9052 local configuration and shared runtime registers.
+/* PLX PCI9052 local configuration and shared runtime registers.
* This structure can be used to access 9052 registers (memory mapped).
*/
typedef struct {
--
2.8.1
next prev parent reply other threads:[~2021-06-15 13:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-15 13:54 [PATCH net-next 0/6] net: pci200syn: clean up some code style issues Peng Li
2021-06-15 13:54 ` [PATCH net-next 1/6] net: pci200syn: remove redundant blank lines Peng Li
2021-06-15 13:54 ` [PATCH net-next 2/6] net: pci200syn: add blank line after declarations Peng Li
2021-06-15 13:54 ` [PATCH net-next 3/6] net: pci200syn: replace comparison to NULL with "!card" Peng Li
2021-06-15 13:54 ` [PATCH net-next 4/6] net: pci200syn: add some required spaces Peng Li
2021-06-15 13:54 ` [PATCH net-next 5/6] net: pci200syn: add necessary () to macro argument Peng Li
2021-06-15 13:54 ` Peng Li [this message]
2021-06-15 18:20 ` [PATCH net-next 0/6] net: pci200syn: 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=1623765263-36775-7-git-send-email-lipeng321@huawei.com \
--to=lipeng321@huawei.com \
--cc=davem@davemloft.net \
--cc=huangguangbin2@huawei.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ms@dev.tdt.de \
--cc=netdev@vger.kernel.org \
--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).