linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
	"David S. Miller" <davem@davemloft.net>,
	Jakub Kicinski <kuba@kernel.org>,
	linux-nfc@lists.01.org, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 03/12] nfc: port100: correct kerneldoc for structure
Date: Fri, 28 May 2021 08:41:51 -0400	[thread overview]
Message-ID: <20210528124200.79655-3-krzysztof.kozlowski@canonical.com> (raw)
In-Reply-To: <20210528124200.79655-1-krzysztof.kozlowski@canonical.com>

The port100_in_rf_setting structure does not contain valid kerneldoc
docummentation, unlike the port100_tg_rf_setting structure.  Correct the
kerneldoc to fix W=1 warnings:

    warning: This comment starts with '/**', but isn't a kernel-doc comment.

Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>
---
 drivers/nfc/port100.c | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/drivers/nfc/port100.c b/drivers/nfc/port100.c
index 8e4d355dc3ae..4df926cc37d0 100644
--- a/drivers/nfc/port100.c
+++ b/drivers/nfc/port100.c
@@ -94,7 +94,7 @@ struct port100;
 typedef void (*port100_send_async_complete_t)(struct port100 *dev, void *arg,
 					      struct sk_buff *resp);
 
-/**
+/*
  * Setting sets structure for in_set_rf command
  *
  * @in_*_set_number: Represent the entry indexes in the port-100 RF Base Table.
@@ -145,7 +145,7 @@ static const struct port100_in_rf_setting in_rf_settings[] = {
 };
 
 /**
- * Setting sets structure for tg_set_rf command
+ * struct port100_tg_rf_setting - Setting sets structure for tg_set_rf command
  *
  * @tg_set_number: Represents the entry index in the port-100 RF Base Table.
  *                 This table contains multiple RF setting sets required for RF
-- 
2.27.0


  parent reply	other threads:[~2021-05-28 12:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-28 12:41 [PATCH 01/12] nfc: fdp: correct kerneldoc for structure Krzysztof Kozlowski
2021-05-28 12:41 ` [PATCH 02/12] nfc: fdp: drop ACPI_PTR from device ID table Krzysztof Kozlowski
2021-05-28 12:41 ` Krzysztof Kozlowski [this message]
2021-05-28 12:41 ` [PATCH 04/12] nfc: pn533: drop of_match_ptr " Krzysztof Kozlowski
2021-05-28 12:41 ` [PATCH 05/12] nfc: mrvl: mark OF device ID tables as maybe unused Krzysztof Kozlowski
2021-05-28 12:41 ` [PATCH 06/12] nfc: mrvl: skip impossible NCI_MAX_PAYLOAD_SIZE check Krzysztof Kozlowski
2021-05-28 12:41 ` [PATCH 07/12] nfc: pn533: mark OF device ID tables as maybe unused Krzysztof Kozlowski
2021-05-28 12:41 ` [PATCH 08/12] nfc: s3fwrn5: " Krzysztof Kozlowski
2021-05-28 12:41 ` [PATCH 09/12] nfc: pn544: mark ACPI and " Krzysztof Kozlowski
2021-05-28 12:41 ` [PATCH 10/12] nfc: st-nci: " Krzysztof Kozlowski
2021-05-28 12:41 ` [PATCH 11/12] nfc: st21nfca: " Krzysztof Kozlowski
2021-05-28 12:42 ` [PATCH 12/12] nfc: st95hf: " Krzysztof Kozlowski
2021-05-28 22:20 ` [PATCH 01/12] nfc: fdp: correct kerneldoc for structure 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=20210528124200.79655-3-krzysztof.kozlowski@canonical.com \
    --to=krzysztof.kozlowski@canonical.com \
    --cc=davem@davemloft.net \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nfc@lists.01.org \
    --cc=netdev@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).