mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Amrit Khera <amritkhera98@gmail.com>
To: gregkh@linuxfoundation.org, lee.jones@linaro.org, arnd@arndb.de,
	johannes@sipsolutions.net, kuba@kernel.org, mail@anirudhrb.com,
	memxor@gmail.com, rdunlap@infradead.org
Cc: devel@driverdev.osuosl.org, linux-kernel@vger.kernel.org,
	Amrit Khera <amritkhera98@gmail.com>
Subject: [PATCH v2] staging: wimax: Fix block comment style issue in stack.c
Date: Sun, 21 Feb 2021 22:07:59 +0530	[thread overview]
Message-ID: <20210221163758.2996-1-amritkhera98@gmail.com> (raw)

This change fixes a checkpatch warning for "Block comments
use * on subsequent lines".

Signed-off-by: Amrit Khera <amritkhera98@gmail.com>
---
 Changes in v2:
 - Removed the comment entirely, as suggested by Greg KH <gregkh@linuxfoundation.org>

 drivers/staging/wimax/stack.c | 10 ----------
 1 file changed, 10 deletions(-)

diff --git a/drivers/staging/wimax/stack.c b/drivers/staging/wimax/stack.c
index ace24a6dfd2d..345a022810ef 100644
--- a/drivers/staging/wimax/stack.c
+++ b/drivers/staging/wimax/stack.c
@@ -57,17 +57,7 @@ MODULE_PARM_DESC(debug,
 
 /*
  * Authoritative source for the RE_STATE_CHANGE attribute policy
- *
- * We don't really use it here, but /me likes to keep the definition
- * close to where the data is generated.
  */
-/*
-static const struct nla_policy wimax_gnl_re_status_change[WIMAX_GNL_ATTR_MAX + 1] = {
-	[WIMAX_GNL_STCH_STATE_OLD] = { .type = NLA_U8 },
-	[WIMAX_GNL_STCH_STATE_NEW] = { .type = NLA_U8 },
-};
-*/
-
 
 /*
  * Allocate a Report State Change message
-- 
2.20.1


             reply	other threads:[~2021-02-21 16:56 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-21 16:37 Amrit Khera [this message]
2021-02-21 18:09 ` Greg KH
2021-02-22  6:15 ` Dan Carpenter

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=20210221163758.2996-1-amritkhera98@gmail.com \
    --to=amritkhera98@gmail.com \
    --cc=arnd@arndb.de \
    --cc=devel@driverdev.osuosl.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=johannes@sipsolutions.net \
    --cc=kuba@kernel.org \
    --cc=lee.jones@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mail@anirudhrb.com \
    --cc=memxor@gmail.com \
    --cc=rdunlap@infradead.org \
    /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®