Messages in this thread Patch in this message | | | From | ira.weiny@intel ... | Subject | [PATCH V2 4/7] Documentation/auxiliary_bus: Clarify __auxiliary_driver_register | Date | Wed, 1 Dec 2021 20:43:02 -0800 |
| |
From: Ira Weiny <ira.weiny@intel.com>
__auxiliary_driver_register is not intended to be called directly unless a custom name is required. Add documentation for this fact.
Signed-off-by: Ira Weiny <ira.weiny@intel.com> --- drivers/base/auxiliary.c | 5 +++++ 1 file changed, 5 insertions(+)
diff --git a/drivers/base/auxiliary.c b/drivers/base/auxiliary.c index 70a8dbcd31b7..7192f7d03a05 100644 --- a/drivers/base/auxiliary.c +++ b/drivers/base/auxiliary.c @@ -225,6 +225,11 @@ EXPORT_SYMBOL_GPL(auxiliary_find_device); * @auxdrv: auxiliary_driver structure * @owner: owning module/driver * @modname: KBUILD_MODNAME for parent driver + * + * The expectation is that users will call the "auxiliary_driver_register" + * macro so that the caller's KBUILD_MODNAME is automatically inserted for the + * modname parameter. Only if a user requires a custom name would this version + * be called directly. */ int __auxiliary_driver_register(struct auxiliary_driver *auxdrv, struct module *owner, const char *modname) -- 2.31.1
| |