From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
To: Simon Horman <horms@kernel.org>,
Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
Jiri Pirko <jiri@resnulli.us>
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] dpll: remove documentation of rclk_dev_name
Date: Mon, 16 Jun 2025 14:04:09 +0100 [thread overview]
Message-ID: <7e41513d-ba2e-49f2-9e3e-af29874cac41@linux.dev> (raw)
In-Reply-To: <20250616-dpll-member-v1-1-8c9e6b8e1fd4@kernel.org>
On 16/06/2025 13:58, Simon Horman wrote:
> Remove documentation of rclk_dev_name member of dpll_device which
> doesn't exist.
>
> Flagged by ./scripts/kernel-doc -none
>
> Introduced by commit 9431063ad323 ("dpll: core: Add DPLL framework base
> functions")
>
> Signed-off-by: Simon Horman <horms@kernel.org>
> ---
> drivers/dpll/dpll_core.h | 1 -
> 1 file changed, 1 deletion(-)
>
> diff --git a/drivers/dpll/dpll_core.h b/drivers/dpll/dpll_core.h
> index 2b6d8ef1cdf3..9b11e637397b 100644
> --- a/drivers/dpll/dpll_core.h
> +++ b/drivers/dpll/dpll_core.h
> @@ -45,7 +45,6 @@ struct dpll_device {
> * @dpll_refs: hold referencees to dplls pin was registered with
> * @parent_refs: hold references to parent pins pin was registered with
> * @prop: pin properties copied from the registerer
> - * @rclk_dev_name: holds name of device when pin can recover clock from it
> * @refcount: refcount
> * @rcu: rcu_head for kfree_rcu()
> **/
>
Thanks!
Reviewed-by: Vadim Fedorenko <vadim.fedorenko@linux.dev>
next prev parent reply other threads:[~2025-06-16 13:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-16 12:58 [PATCH net-next] dpll: remove documentation of rclk_dev_name Simon Horman
2025-06-16 13:04 ` Vadim Fedorenko [this message]
2025-06-18 2:01 ` 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=7e41513d-ba2e-49f2-9e3e-af29874cac41@linux.dev \
--to=vadim.fedorenko@linux.dev \
--cc=arkadiusz.kubalewski@intel.com \
--cc=horms@kernel.org \
--cc=jiri@resnulli.us \
--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 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.