All of lore.kernel.org
 help / color / mirror / Atom feed
From: Bo Sun <bo@mboxify.com>
To: barebox@lists.infradead.org
Subject: [PATCH 3/3] of: base: fix of_match_node function documentation
Date: Fri, 11 Jul 2025 20:27:29 +0800	[thread overview]
Message-ID: <20250711122729.108015-3-bo@mboxify.com> (raw)
In-Reply-To: <20250711122729.108015-1-bo@mboxify.com>

Fix grammar error, correct structure name, and add missing return
value description.

Signed-off-by: Bo Sun <bo@mboxify.com>
---
 drivers/of/base.c | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/drivers/of/base.c b/drivers/of/base.c
index 1439e55a0a..903adb3670 100644
--- a/drivers/of/base.c
+++ b/drivers/of/base.c
@@ -778,11 +778,13 @@ struct device_node *of_find_node_with_property(struct device_node *from,
 EXPORT_SYMBOL(of_find_node_with_property);
 
 /**
- * of_match_node - Tell if an device_node has a matching of_match structure
+ * of_match_node - Tell if a device_node has a matching of_device_id structure
  *      @matches:       array of of device match structures to search in
  *      @node:          the of device structure to match against
  *
  *      Low level utility function used by device matching.
+ *
+ *      Return: pointer to the best matching of_device_id structure, or NULL
  */
 const struct of_device_id *of_match_node(const struct of_device_id *matches,
 					 const struct device_node *node)



  parent reply	other threads:[~2025-07-11 12:31 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-11 12:27 [PATCH 1/3] driver: clean up comment formatting and spacing Bo Sun
2025-07-11 12:27 ` [PATCH 2/3] miitool: clarify help text for default behavior and -s option Bo Sun
2025-07-11 12:53   ` Ahmad Fatoum
2025-07-11 12:27 ` Bo Sun [this message]
2025-07-11 12:55   ` [PATCH 3/3] of: base: fix of_match_node function documentation Ahmad Fatoum
2025-07-11 12:39 ` [PATCH 1/3] driver: clean up comment formatting and spacing Ahmad Fatoum
2025-07-11 13:43   ` Bo Sun
2025-08-05  9:18 ` Sascha Hauer

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=20250711122729.108015-3-bo@mboxify.com \
    --to=bo@mboxify.com \
    --cc=barebox@lists.infradead.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.