From: Lee Jones <lee.jones@linaro.org>
To: lgirdwood@gmail.com, broonie@kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, Lee Jones <lee.jones@linaro.org>,
Tony Lindgren <tony@atomide.com>
Subject: [RESEND 08/10] regulator: cpcap-regulator: Demote kerneldoc header to standard comment
Date: Thu, 25 Jun 2020 20:17:06 +0100 [thread overview]
Message-ID: <20200625191708.4014533-9-lee.jones@linaro.org> (raw)
In-Reply-To: <20200625191708.4014533-1-lee.jones@linaro.org>
Nothing about this comment identifies it as a kerneldoc header.
They're missing all of their struct's property descriptions and
the correct 'struct *' header.
Fixes the following W=1 warning(s):
drivers/regulator/cpcap-regulator.c:99: warning: cannot understand function prototype: 'struct cpcap_regulator '
drivers/regulator/cpcap-regulator.c:337: warning: cannot understand function prototype: 'const struct cpcap_regulator omap4_regulators[] = '
Cc: Tony Lindgren <tony@atomide.com>
Signed-off-by: Lee Jones <lee.jones@linaro.org>
---
drivers/regulator/cpcap-regulator.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/regulator/cpcap-regulator.c b/drivers/regulator/cpcap-regulator.c
index fbf823b830308..221e8db358c9e 100644
--- a/drivers/regulator/cpcap-regulator.c
+++ b/drivers/regulator/cpcap-regulator.c
@@ -89,7 +89,7 @@
*/
#define CPCAP_REG_OFF_MODE_SEC BIT(15)
-/**
+/*
* SoC specific configuration for CPCAP regulator. There are at least three
* different SoCs each with their own parameters: omap3, omap4 and tegra2.
*
@@ -325,7 +325,7 @@ static const unsigned int vvib_val_tbl[] = { 1300000, 1800000, 2000000,
static const unsigned int vusb_val_tbl[] = { 0, 3300000, };
static const unsigned int vaudio_val_tbl[] = { 0, 2775000, };
-/**
+/*
* SoC specific configuration for omap4. The data below is comes from Motorola
* Linux kernel tree. It's basically the values of cpcap_regltr_data,
* cpcap_regulator_mode_values and cpcap_regulator_off_mode_values, see
--
2.25.1
next prev parent reply other threads:[~2020-06-25 19:17 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-25 19:16 [RESEND 00/10] Fix a bunch of W=1 warnings in Regulator Lee Jones
2020-06-25 19:16 ` [RESEND 01/10] regulator: consumer: Supply missing prototypes for 3 core functions Lee Jones
2020-06-25 19:17 ` [RESEND 02/10] regulator: devres: Fix issues with kerneldoc headers Lee Jones
2020-06-25 19:17 ` [RESEND 03/10] regulator: of_regulator: Add missing colon for rdev kerneldoc argument Lee Jones
2020-06-25 19:17 ` [RESEND 04/10] regulator: dbx500-prcmu: Remove unused function dbx500_regulator_testcase() Lee Jones
2020-07-07 12:41 ` Linus Walleij
2020-06-25 19:17 ` [RESEND 05/10] regulator: ab8500: Remove unused embedded struct expand_register Lee Jones
2020-07-07 12:42 ` Linus Walleij
2020-06-25 19:17 ` [RESEND 06/10] regulator: wm8350-regulator: Repair odd formatting in documentation Lee Jones
2020-06-26 10:42 ` Charles Keepax
2020-06-25 19:17 ` [RESEND 07/10] regulator: cpcap-regulator: Remove declared and set, but never used variable 'ignore' Lee Jones
2020-06-29 18:26 ` Tony Lindgren
2020-06-25 19:17 ` Lee Jones [this message]
2020-06-25 19:17 ` [RESEND 09/10] regulator: da9063-regulator: Fix .suspend 'initialized field overwritten' warnings Lee Jones
2020-06-26 8:49 ` Adam Thomson
2020-06-25 19:17 ` [RESEND 10/10] regulator: max14577-regulator: Demote kerneldoc header to standard comment Lee Jones
2020-06-25 19:48 ` [RESEND 00/10] Fix a bunch of W=1 warnings in Regulator Mark Brown
2020-06-26 9:36 ` Lee Jones
2020-06-26 13:35 ` Mark Brown
2020-06-26 15:16 ` Mark Brown
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=20200625191708.4014533-9-lee.jones@linaro.org \
--to=lee.jones@linaro.org \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tony@atomide.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®