From: "Alvin Šipraga" <alvin.sipraga@analog.com>
To: development@redaril.me
Cc: Peter Rosin <peda@lysator.liu.se>,
Linus Walleij <linusw@kernel.org>,
linux-kernel@vger.kernel.org, linux-gpio@vger.kernel.org,
xu.yang_2@nxp.com
Subject: Re: [PATCH] mux: convert to use fwnode interface
Date: Wed, 16 Sep 2026 02:20:27 +0200 [thread overview]
Message-ID: <aqngNh-V7z3L2lP6@analog.com> (raw)
In-Reply-To: <20260915-mux_fwnode-v1-1-ed5a6d8202d4@redaril.me>
On Tue, Sep 15, 2026 at 09:35:21PM +0200, Fabio Forni via B4 Relay wrote:
> @@ -821,23 +825,23 @@ static struct mux_state *__devm_mux_state_get(struct device *dev, const char *mu
> }
>
> /**
> - * devm_mux_state_get_from_np() - Get the mux-state for a device, with resource
> + * devm_mux_state_get_from_swnode() - Get the mux-state for a device, with resource
> * management.
> * @dev: The device that needs a mux-control.
> * @mux_name: The name identifying the mux-control.
> - * @np: the device nodes, use dev->of_node if it is NULL.
> + * @node: the device nodes, use dev's fwnode if it is NULL.
> *
> * Return: Pointer to the mux-state, or an ERR_PTR with a negative errno.
> *
> * The mux-state will automatically be freed on release.
> */
> struct mux_state *
> -devm_mux_state_get_from_np(struct device *dev, const char *mux_name,
> - struct device_node *np)
> +devm_mux_state_get_from_swnode(struct device *dev, const char *mux_name,
> + struct fwnode_handle *node)
Shouldn't it be get_from_fwnode (not swnode)?
Kind regards,
Alvin
prev parent reply other threads:[~2026-09-16 0:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 19:35 Fabio Forni via B4 Relay
2026-09-15 23:26 ` Linus Walleij
2026-09-16 0:20 ` Alvin Šipraga [this message]
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=aqngNh-V7z3L2lP6@analog.com \
--to=alvin.sipraga@analog.com \
--cc=development@redaril.me \
--cc=linusw@kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=peda@lysator.liu.se \
--cc=xu.yang_2@nxp.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®