All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Frank Li <Frank.Li@nxp.com>
Cc: alexandre.belloni@bootlin.com, linux-kernel@vger.kernel.org,
	linux-next@vger.kernel.org, conor.culhane@silvaco.com,
	imx@lists.linux.dev, joe@perches.com,
	linux-i3c@lists.infradead.org,
	zbigniew.lukwinski@linux.intel.com
Subject: Re: [PATCH 1/1] i3c: master: fix kernel-doc check warning
Date: Tue, 9 Jan 2024 09:10:24 +0100	[thread overview]
Message-ID: <20240109091024.40fd1dfb@xps-13> (raw)
In-Reply-To: <20240109052548.2128133-1-Frank.Li@nxp.com>

Hi Frank,

Frank.Li@nxp.com wrote on Tue,  9 Jan 2024 00:25:48 -0500:

> Fix warning found by
> 	'scripts/kernel-doc -v -none include/linux/i3c/master.h'
> 
> include/linux/i3c/master.h:457: warning: Function parameter or member 'enable_hotjoin' not described in 'i3c_master_controller_ops'
> include/linux/i3c/master.h:457: warning: Function parameter or member 'disable_hotjoin' not described in 'i3c_master_controller_ops'
> include/linux/i3c/master.h:499: warning: Function parameter or member 'hotjoin' not described in 'i3c_master_controller'
> 
> Signed-off-by: Frank Li <Frank.Li@nxp.com>

Reviewed-by: Miquel Raynal <miquel.raynal@bootlin.com>

Thanks,
Miquèl

WARNING: multiple messages have this Message-ID (diff)
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Frank Li <Frank.Li@nxp.com>
Cc: alexandre.belloni@bootlin.com, linux-kernel@vger.kernel.org,
	linux-next@vger.kernel.org, conor.culhane@silvaco.com,
	imx@lists.linux.dev, joe@perches.com,
	linux-i3c@lists.infradead.org,
	zbigniew.lukwinski@linux.intel.com
Subject: Re: [PATCH 1/1] i3c: master: fix kernel-doc check warning
Date: Tue, 9 Jan 2024 09:10:24 +0100	[thread overview]
Message-ID: <20240109091024.40fd1dfb@xps-13> (raw)
In-Reply-To: <20240109052548.2128133-1-Frank.Li@nxp.com>

Hi Frank,

Frank.Li@nxp.com wrote on Tue,  9 Jan 2024 00:25:48 -0500:

> Fix warning found by
> 	'scripts/kernel-doc -v -none include/linux/i3c/master.h'
> 
> include/linux/i3c/master.h:457: warning: Function parameter or member 'enable_hotjoin' not described in 'i3c_master_controller_ops'
> include/linux/i3c/master.h:457: warning: Function parameter or member 'disable_hotjoin' not described in 'i3c_master_controller_ops'
> include/linux/i3c/master.h:499: warning: Function parameter or member 'hotjoin' not described in 'i3c_master_controller'
> 
> Signed-off-by: Frank Li <Frank.Li@nxp.com>

Reviewed-by: Miquel Raynal <miquel.raynal@bootlin.com>

Thanks,
Miquèl

-- 
linux-i3c mailing list
linux-i3c@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-i3c

  reply	other threads:[~2024-01-09  8:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-09  5:25 [PATCH 1/1] i3c: master: fix kernel-doc check warning Frank Li
2024-01-09  5:25 ` Frank Li
2024-01-09  8:10 ` Miquel Raynal [this message]
2024-01-09  8:10   ` Miquel Raynal
2024-01-14 22:01 ` Alexandre Belloni
2024-01-14 22:01   ` Alexandre Belloni

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=20240109091024.40fd1dfb@xps-13 \
    --to=miquel.raynal@bootlin.com \
    --cc=Frank.Li@nxp.com \
    --cc=alexandre.belloni@bootlin.com \
    --cc=conor.culhane@silvaco.com \
    --cc=imx@lists.linux.dev \
    --cc=joe@perches.com \
    --cc=linux-i3c@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=zbigniew.lukwinski@linux.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 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.