[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <bdfa93d6-a45f-cc26-bc95-42ef21c7e8c6@axentia.se>
Date: Mon, 3 Jun 2019 16:22:11 +0000
From: Peter Rosin <peda@...ntia.se>
To: Suzuki K Poulose <suzuki.poulose@....com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC: "gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"rafael@...nel.org" <rafael@...nel.org>
Subject: Re: [RFC PATCH 39/57] drivers: mux: Use class_find_device_by_of_node
helper
Hi!
This all sounds like nice changes. First a couple of nitpicks:
From the cover letter, included here to spare most of the others...
> subsystems. This series is an attempt to consolidate the and cleanup
s/the and/and/
On 2019-06-03 17:50, Suzuki K Poulose wrote:
> Use the generic helper to find a device matching the of_node.
>
> Cc: Peter Rosin <peda@...ntia.se>
> Signed-off-by: Suzuki K Poulose <suzuki.poulose@....com>
> ---
> drivers/mux/core.c | 8 +-------
> 1 file changed, 1 insertion(+), 7 deletions(-)
>
> diff --git a/drivers/mux/core.c b/drivers/mux/core.c
> index d1271c1..3591e40 100644
> --- a/drivers/mux/core.c
> +++ b/drivers/mux/core.c
> @@ -405,18 +405,12 @@ int mux_control_deselect(struct mux_control *mux)
> }
> EXPORT_SYMBOL_GPL(mux_control_deselect);
>
> -static int of_dev_node_match(struct device *dev, const void *data)
> -{
> - return dev->of_node == data;
> -}
> -
> /* Note this function returns a reference to the mux_chip dev. */
> static struct mux_chip *of_find_mux_chip_by_node(struct device_node *np)
> {
> struct device *dev;
>
> - dev = class_find_device(&mux_class, NULL, np, of_dev_node_match);
> -
Nitpick #2. Please leave the blank line where it belongs.
However, how can I review this if I do not get to see the patch that
adds the class_find_device_by_of_node function? Please provide a
little bit more context!
Cheers,
Peter
> + dev = class_find_device_by_of_node(&mux_class, NULL, np);
> return dev ? to_mux_chip(dev) : NULL;
> }
>
>
Powered by blists - more mailing lists