The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Frank Li <Frank.Li@nxp.com>
To: linusw@kernel.org, Peter Rosin <peda@axentia.se>,
	Kees Cook <kees@kernel.org>, Frank Li <Frank.Li@nxp.com>,
	Josua Mayer <josua@solid-run.com>,
	Wolfram Sang <wsa+renesas@sang-engineering.com>,
	Thorsten Blum <thorsten.blum@linux.dev>,
	linux-kernel@vger.kernel.org (open list)
Cc: linux-gpio@vger.kernel.org, imx@lists.linux.dev,
	kernel test robot <lkp@intel.com>
Subject: [PATCH ib-mux-pinctrl 1/1] mux: describe np parameter in __devm_mux_state_get()
Date: Thu,  7 May 2026 11:21:14 -0400	[thread overview]
Message-ID: <20260507152117.240612-1-Frank.Li@nxp.com> (raw)

Add a description for the 'np' parameter of __devm_mux_state_get() to fix
build warning.

Reported-by: kernel test robot <lkp@intel.com>
Closes: https://lore.kernel.org/oe-kbuild-all/202605061502.ullLjmtN-lkp@intel.com/
Signed-off-by: Frank Li <Frank.Li@nxp.com>
---
 drivers/mux/core.c | 1 +
 1 file changed, 1 insertion(+)

diff --git a/drivers/mux/core.c b/drivers/mux/core.c
index 2f01acfccf47b..5083e3d19606b 100644
--- a/drivers/mux/core.c
+++ b/drivers/mux/core.c
@@ -771,6 +771,7 @@ static void devm_mux_state_release(struct device *dev, void *res)
  * @dev: The device that needs a mux-state.
  * @mux_name: The name identifying the mux-state.
  * @optional: Whether to return NULL and silence errors when mux doesn't exist.
+ * @np: The device nodes, use dev->of_node if it is NULL.
  * @init: Optional function pointer for mux-state object initialisation.
  * @exit: Optional function pointer for mux-state object cleanup on release.
  *
--
2.43.0


                 reply	other threads:[~2026-05-07 15:22 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20260507152117.240612-1-Frank.Li@nxp.com \
    --to=frank.li@nxp.com \
    --cc=imx@lists.linux.dev \
    --cc=josua@solid-run.com \
    --cc=kees@kernel.org \
    --cc=linusw@kernel.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@intel.com \
    --cc=peda@axentia.se \
    --cc=thorsten.blum@linux.dev \
    --cc=wsa+renesas@sang-engineering.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