mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yang Shen <shenyang39@huawei.com>
To: <kvalo@codeaurora.org>
Cc: <linux-wireless@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	"Yang Shen" <shenyang39@huawei.com>,
	Stanislav Yakovlev <stas.yakovlev@gmail.com>
Subject: [PATCH 06/11] net: intel: iwlwifi: Demote non-compliant kernel-doc headers
Date: Mon, 17 May 2021 13:01:36 +0800	[thread overview]
Message-ID: <20210517050141.61488-7-shenyang39@huawei.com> (raw)
In-Reply-To: <20210517050141.61488-1-shenyang39@huawei.com>

Fixes the following W=1 kernel build warning(s):

 drivers/net/wireless/intel/iwlwifi/mvm/rfi.c:11: warning: This comment starts with '/**', but isn't a kernel-doc comment. Refer Documentation/doc-guide/kernel-doc.rst
 drivers/net/wireless/intel/iwlwifi/mvm/rfi.c:14:1: warning: ‘static’ is not at beginning of declaration [-Wold-style-declaration]

Cc: Stanislav Yakovlev <stas.yakovlev@gmail.com>
Signed-off-by: Yang Shen <shenyang39@huawei.com>
---
 drivers/net/wireless/intel/iwlwifi/mvm/rfi.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/net/wireless/intel/iwlwifi/mvm/rfi.c b/drivers/net/wireless/intel/iwlwifi/mvm/rfi.c
index 0b818067067c..f1ed73c9f3dd 100644
--- a/drivers/net/wireless/intel/iwlwifi/mvm/rfi.c
+++ b/drivers/net/wireless/intel/iwlwifi/mvm/rfi.c
@@ -7,11 +7,11 @@
 #include "fw/api/commands.h"
 #include "fw/api/phy-ctxt.h"

-/**
+/*
  * DDR needs frequency in units of 16.666MHz, so provide FW with the
  * frequency values in the adjusted format.
  */
-const static struct iwl_rfi_lut_entry iwl_rfi_table[IWL_RFI_LUT_SIZE] = {
+static const struct iwl_rfi_lut_entry iwl_rfi_table[IWL_RFI_LUT_SIZE] = {
 	/* LPDDR4 */

 	/* frequency 3733MHz */
--
2.17.1


  parent reply	other threads:[~2021-05-17  8:15 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-17  5:01 [PATCH 00/11] Rid W=1 warnings in wireless Yang Shen
2021-05-17  5:01 ` [PATCH 01/11] net: ath: ath5k: Fix wrong function name in comments Yang Shen
2021-06-15 14:01   ` Kalle Valo
2021-05-17  5:01 ` [PATCH 02/11] net: ath: " Yang Shen
2021-05-17  5:01 ` [PATCH 03/11] net: ath: wil6210: " Yang Shen
2021-05-17  5:01 ` [PATCH 04/11] net: broadcom: brcmfmac: Demote non-compliant kernel-doc headers Yang Shen
2021-05-19 12:41   ` Arend van Spriel
2021-06-15 10:37   ` [04/11] " Kalle Valo
2021-05-17  5:01 ` [PATCH 05/11] net: intel: ipw2x00: Fix wrong function name in comments Yang Shen
2021-05-17 16:30   ` Stanislav Yakovlev
2021-06-15 13:12   ` [05/11] " Kalle Valo
2021-06-18  7:00     ` Yang Shen
2021-05-17  5:01 ` Yang Shen [this message]
2021-05-18  3:08   ` [PATCH 06/11] net: intel: iwlwifi: Demote non-compliant kernel-doc headers Yang Shen
2021-05-17  5:01 ` [PATCH 07/11] net: marvell: libertas_tf: Fix wrong function name in comments Yang Shen
2021-06-15 13:11   ` [07/11] " Kalle Valo
2021-05-17  5:01 ` [PATCH 08/11] net: realtek: rtlwifi: " Yang Shen
2021-05-17  5:01 ` [PATCH 09/11] net: rsi: Fix missing " Yang Shen
2021-05-17  5:01 ` [PATCH 10/11] net: ti: wl1251: " Yang Shen
2021-06-15 13:39   ` [10/11] " Kalle Valo
2021-05-17  5:01 ` [PATCH 11/11] net: ti: wlcore: " Yang Shen

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=20210517050141.61488-7-shenyang39@huawei.com \
    --to=shenyang39@huawei.com \
    --cc=kvalo@codeaurora.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=stas.yakovlev@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

all inboxes | Powered by JetHome®