Thread (73 messages) 73 messages, 8 authors, 2023-07-17

Re: [RFC PATCH v8 04/10] dpll: netlink: Add DPLL framework base functions

From: Jiri Pirko <jiri@resnulli.us>
Date: 2023-06-21 11:53:35
Also in: intel-wired-lan, linux-clk, linux-doc, linux-rdma, lkml

Wed, Jun 21, 2023 at 01:18:59PM CEST, poros@redhat.com wrote:
Arkadiusz Kubalewski píše v Pá 09. 06. 2023 v 14:18 +0200:
quoted
From: Vadim Fedorenko <vadim.fedorenko@linux.dev>
[...]

Could you perhaps cut out the text you don't comment? Saves some time
finding your reply.

quoted
+static int
+dpll_set_from_nlattr(struct dpll_device *dpll, struct genl_info
*info)
+{
+       const struct dpll_device_ops *ops = dpll_device_ops(dpll);
+       struct nlattr *tb[DPLL_A_MAX + 1];
+       int ret = 0;
+
+       nla_parse(tb, DPLL_A_MAX, genlmsg_data(info->genlhdr),
+                 genlmsg_len(info->genlhdr), NULL, info->extack);
+       if (tb[DPLL_A_MODE]) {
Hi,

Here should be something like:
              if (!ops->mode_set)
                      return -EOPNOTSUPP;
Why? All drivers implement that.
I believe that it's actullaly better that way. For a called setting up
the same mode it is the dpll in, there should be 0 return by the driver.
Note that driver holds this value. I'd like to keep this code as it is.

[...]
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help