public inbox for linux-clk@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <simon.horman@corigine.com>
To: Vadim Fedorenko <vadim.fedorenko@linux.dev>
Cc: Jakub Kicinski <kuba@kernel.org>, Jiri Pirko <jiri@resnulli.us>,
	Arkadiusz Kubalewski <arkadiusz.kubalewski@intel.com>,
	Jonathan Lemon <jonathan.lemon@gmail.com>,
	Paolo Abeni <pabeni@redhat.com>,
	Milena Olech <milena.olech@intel.com>,
	Michal Michalik <michal.michalik@intel.com>,
	linux-arm-kernel@lists.infradead.org, poros@redhat.com,
	mschmidt@redhat.com, netdev@vger.kernel.org,
	linux-clk@vger.kernel.org, Bart Van Assche <bvanassche@acm.org>
Subject: Re: [PATCH net-next 06/11] dpll: netlink: Add DPLL framework base functions
Date: Mon, 24 Jul 2023 18:34:06 +0200	[thread overview]
Message-ID: <ZL6n/g97lrtLH7Ev@corigine.com> (raw)
In-Reply-To: <20230720091903.297066-7-vadim.fedorenko@linux.dev>

On Thu, Jul 20, 2023 at 10:18:58AM +0100, Vadim Fedorenko wrote:
> DPLL framework is used to represent and configure DPLL devices
> in systems. Each device that has DPLL and can configure inputs
> and outputs can use this framework.

Hi Vadim,

some minor feedback from my side.

> 
> Implement dpll netlink framework functions for enablement of dpll
> subsytem netlink family.

subsytem -> subsystem

...

> diff --git a/drivers/dpll/dpll_netlink.c b/drivers/dpll/dpll_netlink.c

...

> +/**
> + * dpll_msg_add_pin_handle - attach pin handle attribute to a given message
> + * @msg: pointer to sk_buff message to attach a pin handle
> + * @pin: pin pointer
> + *
> + * Return:
> + * * 0 - success
> + * * -EMSGSIZE - no space in message to attach pin handle
> + */
> +int dpll_msg_add_pin_handle(struct sk_buff *msg, struct dpll_pin *pin)

This function seems to only be used in this file.
Should it be static.

...

> +static int
> +dpll_msg_add_pin_on_dpll_state(struct sk_buff *msg, struct dpll_pin *pin,
> +			       struct dpll_pin_ref *ref,
> +			       struct netlink_ext_ack *extack)
> +{
> +	const struct dpll_pin_ops *ops = dpll_pin_ops(ref);
> +	struct dpll_device *dpll = ref->dpll;
> +	enum dpll_pin_state state;
> +	int ret;
> +
> +

nit: one blank line is enough

...

> +static int
> +dpll_msg_add_pin_freq(struct sk_buff *msg, struct dpll_pin *pin,
> +		      struct dpll_pin_ref *ref, struct netlink_ext_ack *extack)
> +{
> +	const struct dpll_pin_ops *ops = dpll_pin_ops(ref);
> +	struct dpll_device *dpll = ref->dpll;
> +	struct nlattr *nest;
> +	int fs, ret;
> +	u64 freq;
> +
> +	if (!ops->frequency_get)
> +		return 0;
> +	ret = ops->frequency_get(pin, dpll_pin_on_dpll_priv(dpll, pin), dpll,
> +				 dpll_priv(dpll), &freq, extack);
> +	if (ret)
> +		return ret;
> +	if (nla_put_64bit(msg, DPLL_A_PIN_FREQUENCY, sizeof(freq), &freq, 0))
> +		return -EMSGSIZE;
> +	for (fs = 0; fs < pin->prop->freq_supported_num; fs++) {
> +		nest = nla_nest_start(msg, DPLL_A_PIN_FREQUENCY_SUPPORTED);
> +		if (!nest)
> +			return -EMSGSIZE;
> +		freq = pin->prop->freq_supported[fs].min;
> +		if (nla_put_64bit(msg, DPLL_A_PIN_FREQUENCY_MIN, sizeof(freq),
> +				   &freq, 0)) {

nit: The indention of the line above isn't quite right.
     There is one space too many.

> +			nla_nest_cancel(msg, nest);
> +			return -EMSGSIZE;
> +		}
> +		freq = pin->prop->freq_supported[fs].max;
> +		if (nla_put_64bit(msg, DPLL_A_PIN_FREQUENCY_MAX, sizeof(freq),
> +				   &freq, 0)) {

Ditto.

> +			nla_nest_cancel(msg, nest);
> +			return -EMSGSIZE;
> +		}
> +		nla_nest_end(msg, nest);
> +	}
> +
> +	return 0;
> +}

...

> +static int
> +dpll_device_event_send(enum dpll_cmd event, struct dpll_device *dpll)
> +{
> +	struct sk_buff *msg;
> +	void *hdr;
> +	int ret;
> +
> +	if (WARN_ON(!xa_get_mark(&dpll_device_xa, dpll->id, DPLL_REGISTERED)))
> +		return -ENODEV;
> +	msg = genlmsg_new(NLMSG_GOODSIZE, GFP_KERNEL);
> +	if (!msg)
> +		return -ENOMEM;
> +	hdr = genlmsg_put(msg, 0, 0, &dpll_nl_family, 0, event);
> +	if (!hdr)
> +		goto err_free_msg;

ret is uninitialised here, but it is used in the error path.

This is flagged by a clang-16 W=1 build, and Smatch.

> +	ret = dpll_device_get_one(dpll, msg, NULL);
> +	if (ret)
> +		goto err_cancel_msg;
> +	genlmsg_end(msg, hdr);
> +	genlmsg_multicast(&dpll_nl_family, msg, 0, 0, GFP_KERNEL);
> +
> +	return 0;
> +
> +err_cancel_msg:
> +	genlmsg_cancel(msg, hdr);
> +err_free_msg:
> +	nlmsg_free(msg);
> +
> +	return ret;
> +}

...

> +int __dpll_device_change_ntf(struct dpll_device *dpll)
> +{
> +	return dpll_device_event_send(DPLL_CMD_DEVICE_CHANGE_NTF, dpll);
> +}

Should this function be static?

...

> +static int
> +dpll_pin_event_send(enum dpll_cmd event, struct dpll_pin *pin)
> +{
> +	struct sk_buff *msg;
> +	void *hdr;
> +	int ret;
> +
> +	if (WARN_ON(!xa_get_mark(&dpll_pin_xa, pin->id, DPLL_REGISTERED)))
> +		return -ENODEV;
> +
> +	msg = genlmsg_new(NLMSG_GOODSIZE, GFP_KERNEL);
> +	if (!msg)
> +		return -ENOMEM;
> +
> +	hdr = genlmsg_put(msg, 0, 0, &dpll_nl_family, 0, event);
> +	if (!hdr)
> +		goto err_free_msg;

It looks like ret is used uninitialised here too.

> +	ret = dpll_cmd_pin_get_one(msg, pin, NULL);
> +	if (ret)
> +		goto err_cancel_msg;
> +	genlmsg_end(msg, hdr);
> +	genlmsg_multicast(&dpll_nl_family, msg, 0, 0, GFP_KERNEL);
> +
> +	return 0;
> +
> +err_cancel_msg:
> +	genlmsg_cancel(msg, hdr);
> +err_free_msg:
> +	nlmsg_free(msg);
> +
> +	return ret;
> +}

...

> +void
> +dpll_unlock_doit(const struct genl_split_ops *ops, struct sk_buff *skb,
> +		   struct genl_info *info)

The indentation of the line above is not correct.
There are two spaces too many.

...

> +void dpll_netlink_finish(void)
> +{
> +	genl_unregister_family(&dpll_nl_family);
> +}

Should this function be static?

...

  reply	other threads:[~2023-07-24 16:34 UTC|newest]

Thread overview: 62+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-20  9:18 [PATCH net-next 00/11] Create common DPLL configuration API Vadim Fedorenko
2023-07-20  9:18 ` [PATCH net-next 01/11] tools: ynl-gen: fix enum index in _decode_enum(..) Vadim Fedorenko
2023-07-20 13:40   ` Jiri Pirko
2023-07-20 13:58     ` Kubalewski, Arkadiusz
2023-07-20 14:48       ` Vadim Fedorenko
2023-07-20  9:18 ` [PATCH net-next 02/11] tools: ynl-gen: fix parse multi-attr enum attribute Vadim Fedorenko
2023-07-20  9:18 ` [PATCH net-next 03/11] dpll: documentation on DPLL subsystem interface Vadim Fedorenko
2023-07-20 13:47   ` Jiri Pirko
2023-07-20  9:18 ` [PATCH net-next 04/11] dpll: spec: Add Netlink spec in YAML Vadim Fedorenko
2023-07-24 15:52   ` Simon Horman
2023-07-20  9:18 ` [PATCH net-next 05/11] dpll: core: Add DPLL framework base functions Vadim Fedorenko
2023-07-24 15:56   ` Simon Horman
2023-07-20  9:18 ` [PATCH net-next 06/11] dpll: netlink: " Vadim Fedorenko
2023-07-24 16:34   ` Simon Horman [this message]
2023-08-01 12:23   ` Jiri Pirko
2023-07-20  9:18 ` [PATCH net-next 07/11] netdev: expose DPLL pin handle for netdevice Vadim Fedorenko
2023-08-01 13:23   ` Vadim Fedorenko
2023-08-01 15:12     ` Vadim Fedorenko
2023-07-20  9:19 ` [PATCH net-next 08/11] ice: add admin commands to access cgu configuration Vadim Fedorenko
2023-07-24 17:21   ` Simon Horman
2023-07-28 12:46     ` Kubalewski, Arkadiusz
2023-07-20  9:19 ` [PATCH 09/11] ice: implement dpll interface to control cgu Vadim Fedorenko
2023-07-20 14:08   ` Jiri Pirko
2023-07-20 17:31     ` Kubalewski, Arkadiusz
2023-07-21  7:33       ` Jiri Pirko
2023-07-21 11:17         ` Kubalewski, Arkadiusz
2023-07-21 12:02           ` Jiri Pirko
2023-07-21 13:36             ` Kubalewski, Arkadiusz
2023-07-21 15:45               ` Jiri Pirko
2023-07-21 19:48                 ` Kubalewski, Arkadiusz
2023-07-22  6:37                   ` Jiri Pirko
2023-07-24 15:03                     ` Kubalewski, Arkadiusz
2023-07-25  8:03                       ` Jiri Pirko
2023-07-25 14:01                         ` Kubalewski, Arkadiusz
2023-07-26  6:38                           ` Jiri Pirko
2023-07-26 21:11                             ` Kubalewski, Arkadiusz
2023-07-27 10:28                               ` Vadim Fedorenko
2023-07-25 22:49             ` Jakub Kicinski
2023-07-26 15:20               ` Paolo Abeni
2023-07-26 21:10                 ` Kubalewski, Arkadiusz
2023-07-31 12:08                 ` Jiri Pirko
2023-07-26 21:08               ` Kubalewski, Arkadiusz
2023-07-31 12:11               ` Jiri Pirko
2023-07-22  2:08         ` Jakub Kicinski
2023-07-21 11:39   ` Jiri Pirko
2023-07-28 23:03     ` Kubalewski, Arkadiusz
2023-07-31 12:19       ` Jiri Pirko
2023-08-01 14:50         ` Kubalewski, Arkadiusz
2023-08-02  6:57           ` Jiri Pirko
2023-08-02 15:48             ` Kubalewski, Arkadiusz
2023-08-03  8:02               ` Jiri Pirko
2023-08-04  8:58                 ` Kubalewski, Arkadiusz
2023-07-24 17:41   ` Simon Horman
2023-07-24 17:58     ` Vadim Fedorenko
2023-07-28 23:10       ` Kubalewski, Arkadiusz
2023-07-20  9:19 ` [PATCH 10/11] ptp_ocp: implement DPLL ops Vadim Fedorenko
2023-07-21 15:51   ` Jiri Pirko
2023-07-20  9:19 ` [PATCH 11/11] mlx5: Implement SyncE support using DPLL infrastructure Vadim Fedorenko
2023-07-21  7:48 ` [PATCH net-next 00/11] Create common DPLL configuration API Jiri Pirko
2023-07-21 11:14 ` Jiri Pirko
2023-07-21 14:42   ` Vadim Fedorenko
2023-07-21 15:46     ` Jiri Pirko

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=ZL6n/g97lrtLH7Ev@corigine.com \
    --to=simon.horman@corigine.com \
    --cc=arkadiusz.kubalewski@intel.com \
    --cc=bvanassche@acm.org \
    --cc=jiri@resnulli.us \
    --cc=jonathan.lemon@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=michal.michalik@intel.com \
    --cc=milena.olech@intel.com \
    --cc=mschmidt@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=poros@redhat.com \
    --cc=vadim.fedorenko@linux.dev \
    /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