summaryrefslogtreecommitdiff
path: root/drivers/base/core.c
diff options
context:
space:
mode:
authorYuesong Li <liyuesong@vivo.com>2024-08-21 12:04:32 +0800
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2024-09-03 12:59:17 +0200
commit4a74f22386ccb1ddd06eb242bdd02548a7199bda (patch)
treed0527af954a5ac3d6d63c956df00dbc79a838331 /drivers/base/core.c
parentb45ed06f46737f8c2ee65698f4305409f2386674 (diff)
driver:base:core: Adding a "Return:" line in comment for device_link_add()
The original document doesn't explain the return value directly which leads to confusing in error checking. You can find the reason here: Link: https://lore.kernel.org/all/1d4c39e109bcf288d5900670e024a315.sboyd@kernel.org/ Signed-off-by: Yuesong Li <liyuesong@vivo.com> Link: https://lore.kernel.org/r/20240821040432.4049183-1-liyuesong@vivo.com Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Diffstat (limited to 'drivers/base/core.c')
-rw-r--r--drivers/base/core.c3
1 files changed, 3 insertions, 0 deletions
diff --git a/drivers/base/core.c b/drivers/base/core.c
index 4bc8b88d697e..ec2197aec0b7 100644
--- a/drivers/base/core.c
+++ b/drivers/base/core.c
@@ -673,6 +673,9 @@ postcore_initcall(devlink_class_init);
* @supplier: Supplier end of the link.
* @flags: Link flags.
*
+ * Return: On success, a device_link struct will be returned.
+ * On error or invalid flag settings, NULL will be returned.
+ *
* The caller is responsible for the proper synchronization of the link creation
* with runtime PM. First, setting the DL_FLAG_PM_RUNTIME flag will cause the
* runtime PM framework to take the link into account. Second, if the