driver core: Fix a couple of typos
PATCH 1/1 driver core: Fix a couple of typos
From: Thierry Reding <[email protected]>
These were just some minor typos that have crept in recently and are easily fixed.
Signed-off-by Thierry Reding <[email protected]>
--- drivers/base/core.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/base/core.c +2 -2
@@ -468,7 +468,7 @@ postcore_initcall(devlink_class_init);* 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 * DL_FLAG_RPM_ACTIVE flag is set in addition to it, the supplier devices will -* be forced into the active metastate and reference-counted upon the creation +* be forced into the active meta state and reference-counted upon the creation * of the link. If DL_FLAG_PM_RUNTIME is not set, DL_FLAG_RPM_ACTIVE will be * ignored. *
@@ -491,7 +491,7 @@ postcore_initcall(devlink_class_init);* Also, if DL_FLAG_STATELESS, DL_FLAG_AUTOREMOVE_CONSUMER and * DL_FLAG_AUTOREMOVE_SUPPLIER are not set in @flags (that is, a persistent * managed device link is being added), the DL_FLAG_AUTOPROBE_CONSUMER flag can -* be used to request the driver core to automaticall probe for a consmer +* be used to request the driver core to automatically probe for a consumer * driver after successfully binding a driver to the supplier device. * * The combination of DL_FLAG_STATELESS and one of DL_FLAG_AUTOREMOVE_CONSUMER,
Signature · 1 line
2.29.2
Quoted 7 lines · Thierry Reding
From: Thierry Reding <[email protected]>
These were just some minor typos that have crept in recently and are easily fixed.
Signed-off-by Thierry Reding <[email protected]>
Reviewed-by Rafael J. Wysocki <[email protected]>
Quoted 29 lines
--- drivers/base/core.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)drivers/base/core.c +2
-3@@ -468,7 +468,7 @@ postcore_initcall(devlink_class_init);* 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 * DL_FLAG_RPM_ACTIVE flag is set in addition to it, the supplier devices will -* be forced into the active metastate and reference-counted upon the creation +* be forced into the active meta state and reference-counted upon the creation * of the link. If DL_FLAG_PM_RUNTIME is not set, DL_FLAG_RPM_ACTIVE will be * ignored. * @@ -491,7 +491,7 @@ postcore_initcall(devlink_class_init);* Also, if DL_FLAG_STATELESS, DL_FLAG_AUTOREMOVE_CONSUMER and * DL_FLAG_AUTOREMOVE_SUPPLIER are not set in @flags (that is, a persistent * managed device link is being added), the DL_FLAG_AUTOPROBE_CONSUMER flag can -* be used to request the driver core to automaticall probe for a consmer +* be used to request the driver core to automatically probe for a consumer * driver after successfully binding a driver to the supplier device. * * The combination of DL_FLAG_STATELESS and one of DL_FLAG_AUTOREMOVE_CONSUMER, -- 2.29.2