From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: linux-kernel@vger.kernel.org
Cc: Johannes Berg <johannes@sipsolutions.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J . Wysocki" <rafael@kernel.org>,
Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Subject: [PATCH 0/7] drivers/base: remove kernel-doc warnings
Date: Wed, 31 Mar 2021 18:26:07 -0500 [thread overview]
Message-ID: <20210331232614.304591-1-pierre-louis.bossart@linux.intel.com> (raw)
Trivial fixes to reduce the number of warnings with make W=1
After this patchset, there are still a number of false positives
reported, I left them as is.
drivers/base/power/runtime.c:347: warning: Excess function parameter
'dev' description in '__rpm_callback'
drivers/base/platform.c:1545:20: warning: no previous prototype for
‘early_platform_cleanup’ [-Wmissing-prototypes]
1545 | void __weak __init early_platform_cleanup(void) { }
| ^~~~~~~~~~~~~~~~~~~~~~
drivers/base/attribute_container.c:304: warning: Function parameter or
member 'fn' not described in 'attribute_container_device_trigger_safe'
drivers/base/attribute_container.c:304: warning: Function parameter or
member 'undo' not described in
'attribute_container_device_trigger_safe'
drivers/base/attribute_container.c:357: warning: Function parameter or
member 'fn' not described in 'attribute_container_device_trigger'
drivers/base/module.c: In function ‘module_add_driver’:
drivers/base/module.c:36:6: warning: variable ‘no_warn’ set but not
used [-Wunused-but-set-variable]
36 | int no_warn;
| ^~~~~~~
Pierre-Louis Bossart (7):
driver core: remove kernel-doc warnings
driver core: attribute_container: remove kernel-doc warnings
PM: runtime: remove kernel-doc warnings
PM: wakeup: fix kernel-doc warnings and fix typos
PM: clk: remove kernel-doc warning
platform-msi: fix kernel-doc warnings
devcoredump: fix kernel-doc warning
drivers/base/attribute_container.c | 4 ++++
drivers/base/core.c | 11 ++++++-----
drivers/base/devcoredump.c | 4 ++--
drivers/base/platform-msi.c | 3 ++-
drivers/base/power/clock_ops.c | 2 +-
drivers/base/power/runtime.c | 2 +-
drivers/base/power/wakeup.c | 17 +++++++++--------
7 files changed, 25 insertions(+), 18 deletions(-)
base-commit: 7a43c78d0573e0bbbb0456b033e2b9a895b89464
--
2.25.1
next reply other threads:[~2021-03-31 23:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-31 23:26 Pierre-Louis Bossart [this message]
2021-03-31 23:26 ` [PATCH 1/7] driver core: remove kernel-doc warnings Pierre-Louis Bossart
2021-03-31 23:26 ` [PATCH 2/7] driver core: attribute_container: " Pierre-Louis Bossart
2021-03-31 23:26 ` [PATCH 3/7] PM: runtime: " Pierre-Louis Bossart
2021-04-01 13:40 ` Rafael J. Wysocki
2021-04-01 14:13 ` Pierre-Louis Bossart
2021-04-02 14:24 ` Greg Kroah-Hartman
2021-04-07 17:23 ` Rafael J. Wysocki
2021-03-31 23:26 ` [PATCH 4/7] PM: wakeup: fix kernel-doc warnings and fix typos Pierre-Louis Bossart
2021-03-31 23:26 ` [PATCH 5/7] PM: clk: remove kernel-doc warning Pierre-Louis Bossart
2021-03-31 23:26 ` [PATCH 6/7] platform-msi: fix kernel-doc warnings Pierre-Louis Bossart
2021-03-31 23:26 ` [PATCH 7/7] devcoredump: fix kernel-doc warning Pierre-Louis Bossart
2021-04-01 7:07 ` Johannes Berg
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=20210331232614.304591-1-pierre-louis.bossart@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=johannes@sipsolutions.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.