From: Wolfram Sang <wsa@kernel.org>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Cc: Seth Heasley <seth.heasley@intel.com>,
Neil Horman <nhorman@tuxdriver.com>,
linux-i2c@vger.kernel.org
Subject: Re: [PATCH v1] i2c: ismt: Describe parameters in kernel doc
Date: Wed, 5 Aug 2020 11:39:49 +0200 [thread overview]
Message-ID: <20200805093949.GQ1229@kunai> (raw)
In-Reply-To: <20200722134355.46098-1-andriy.shevchenko@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 2281 bytes --]
On Wed, Jul 22, 2020 at 04:43:55PM +0300, Andy Shevchenko wrote:
> Kernel doc validation script complains:
>
> CHECK .../drivers/i2c/busses/i2c-ismt.c
> .../i2c-ismt.c:182: warning: cannot understand function prototype: 'const struct pci_device_id ismt_ids[] = '
> .../i2c-ismt.c:202: warning: Function parameter or member 'dev' not described in '__ismt_desc_dump'
> .../i2c-ismt.c:202: warning: Function parameter or member 'desc' not described in '__ismt_desc_dump'
> .../i2c-ismt.c:649: warning: cannot understand function prototype: 'const struct i2c_algorithm smbus_algorithm = '
>
> Fix corresponding descriptions to make reader and kernel doc validator happy.
>
> Signed-off-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
> ---
Seth, Neil?
> drivers/i2c/busses/i2c-ismt.c | 10 ++--------
> 1 file changed, 2 insertions(+), 8 deletions(-)
>
> diff --git a/drivers/i2c/busses/i2c-ismt.c b/drivers/i2c/busses/i2c-ismt.c
> index 6ba91d4a4ce4..078e01799c83 100644
> --- a/drivers/i2c/busses/i2c-ismt.c
> +++ b/drivers/i2c/busses/i2c-ismt.c
> @@ -176,9 +176,6 @@ struct ismt_priv {
> u8 buffer[I2C_SMBUS_BLOCK_MAX + 16]; /* temp R/W data buffer */
> };
>
> -/**
> - * ismt_ids - PCI device IDs supported by this driver
> - */
> static const struct pci_device_id ismt_ids[] = {
> { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_S1200_SMT0) },
> { PCI_DEVICE(PCI_VENDOR_ID_INTEL, PCI_DEVICE_ID_INTEL_S1200_SMT1) },
> @@ -197,6 +194,8 @@ MODULE_PARM_DESC(bus_speed, "Bus Speed in kHz (0 = BIOS default)");
>
> /**
> * __ismt_desc_dump() - dump the contents of a specific descriptor
> + * @dev: the iSMT device
> + * @desc: the iSMT hardware descriptor
> */
> static void __ismt_desc_dump(struct device *dev, const struct ismt_desc *desc)
> {
> @@ -642,11 +641,6 @@ static u32 ismt_func(struct i2c_adapter *adap)
> I2C_FUNC_SMBUS_PEC;
> }
>
> -/**
> - * smbus_algorithm - the adapter algorithm and supported functionality
> - * @smbus_xfer: the adapter algorithm
> - * @functionality: functionality supported by the adapter
> - */
> static const struct i2c_algorithm smbus_algorithm = {
> .smbus_xfer = ismt_access,
> .functionality = ismt_func,
> --
> 2.27.0
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-08-05 9:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-22 13:43 [PATCH v1] i2c: ismt: Describe parameters in kernel doc Andy Shevchenko
2020-08-05 9:39 ` Wolfram Sang [this message]
2020-09-21 9:57 ` Wolfram Sang
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=20200805093949.GQ1229@kunai \
--to=wsa@kernel.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linux-i2c@vger.kernel.org \
--cc=nhorman@tuxdriver.com \
--cc=seth.heasley@intel.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;
as well as URLs for NNTP newsgroup(s).