public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Angelo Dureghello <angelo@kernel-space.org>
To: myungjoo.ham@samsung.com, cw00.choi@samsung.com
Cc: linux-kernel@vger.kernel.org,
	Angelo Dureghello <adureghello@baylibre.com>
Subject: [PATCH] extcon: fix devm_extcon_dev_register comment
Date: Wed, 11 Feb 2026 16:54:34 +0100	[thread overview]
Message-ID: <20260211155434.7389-1-angelo@kernel-space.org> (raw)

From: Angelo Dureghello <adureghello@baylibre.com>

Fix incomplete function comment.

Signed-off-by: Angelo Dureghello <adureghello@baylibre.com>
---
 drivers/extcon/devres.c | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/drivers/extcon/devres.c b/drivers/extcon/devres.c
index f9d52e8ec5cf..7a23950ba82f 100644
--- a/drivers/extcon/devres.c
+++ b/drivers/extcon/devres.c
@@ -106,9 +106,11 @@ EXPORT_SYMBOL_GPL(devm_extcon_dev_free);
  * @dev:	the device owning the extcon device being created
  * @edev:	the extcon device to be registered
  *
- * this function, that extcon device is automatically unregistered on driver
- * detach. Internally this function calls extcon_dev_register() function.
- * To get more information, refer that function.
+ * This function registers extcon device. Using this function extcon device is
+ * automatically unregistered on driver detach.
+ *
+ * Internally this function calls extcon_dev_register() function. To get more
+ * information, refer that function.
  *
  * If extcon device is registered with this function and the device needs to be
  * unregistered separately, devm_extcon_dev_unregister() should be used.
-- 
2.52.0


                 reply	other threads:[~2026-02-11 15:58 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=20260211155434.7389-1-angelo@kernel-space.org \
    --to=angelo@kernel-space.org \
    --cc=adureghello@baylibre.com \
    --cc=cw00.choi@samsung.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=myungjoo.ham@samsung.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