mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Daniel West <daniel.west.dev@gmail.com>
To: Larry.Finger@lwfinger.net
Cc: gregkh@linuxfoundation.org, insafonov@gmail.com,
	daniel.west.dev@gmail.com, gustavoars@kernel.org,
	andrealmeidap1996@gmail.com, yepeilin.cs@gmail.com,
	devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org
Subject: [PATCH 8455/8455] staging: rtl8188eu: core: fixed a comment format issue.
Date: Sat, 19 Dec 2020 14:43:12 -0800	[thread overview]
Message-ID: <20201219224312.380126-1-daniel.west.dev@gmail.com> (raw)

Fixed a checkpatch warning:

WARNING: Block comments use * on subsequent lines
 #4595: FILE: drivers/staging/rtl8188eu/core/rtw_mlme_ext.c:4595:
+/****************************************************************************
+

The code is full of comments like this. Should the coding style
be inforced here, even when there is a logic to the way the code
was broken up?

Signed-off-by: Daniel West <daniel.west.dev@gmail.com>
---
 drivers/staging/rtl8188eu/core/rtw_mlme_ext.c | 9 ++++-----
 1 file changed, 4 insertions(+), 5 deletions(-)

diff --git a/drivers/staging/rtl8188eu/core/rtw_mlme_ext.c b/drivers/staging/rtl8188eu/core/rtw_mlme_ext.c
index 8794907a39f4..adf2788a416f 100644
--- a/drivers/staging/rtl8188eu/core/rtw_mlme_ext.c
+++ b/drivers/staging/rtl8188eu/core/rtw_mlme_ext.c
@@ -4591,11 +4591,10 @@ void mlmeext_sta_del_event_callback(struct adapter *padapter)
 	}
 }
 
-/****************************************************************************
-
-Following are the functions for the timer handlers
-
-*****************************************************************************/
+/*
+ *
+ *Following are the functions for the timer handlers
+ */
 
 static u8 chk_ap_is_alive(struct adapter *padapter, struct sta_info *psta)
 {
-- 
2.25.1


             reply	other threads:[~2020-12-19 22:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-19 22:43 Daniel West [this message]
2020-12-20 15:29 ` Kari Argillander
2020-12-28 14:09 ` Greg KH
2020-12-28 19:47   ` Joe Perches

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=20201219224312.380126-1-daniel.west.dev@gmail.com \
    --to=daniel.west.dev@gmail.com \
    --cc=Larry.Finger@lwfinger.net \
    --cc=andrealmeidap1996@gmail.com \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=gustavoars@kernel.org \
    --cc=insafonov@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=yepeilin.cs@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

Powered by JetHome