From: Thierry Reding Date: Fri, 27 Nov 2020 10:46:30 +0000 (+0100) Subject: driver core: Fix a couple of typos X-Git-Tag: v5.11-rc1~165^2~13 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=d475f8ea98a039e51d27f5557dc17333cf8a52f6;p=thirdparty%2Fkernel%2Flinux.git driver core: Fix a couple of typos These were just some minor typos that have crept in recently and are easily fixed. Reviewed-by: Rafael J. Wysocki Signed-off-by: Thierry Reding Link: https://lore.kernel.org/r/20201127104630.1839171-1-thierry.reding@gmail.com Signed-off-by: Greg Kroah-Hartman --- diff --git a/drivers/base/core.c b/drivers/base/core.c index 63edb8bd9d7dd..25e08e5f40bd9 100644 --- a/drivers/base/core.c +++ b/drivers/base/core.c @@ -561,7 +561,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. * @@ -584,7 +584,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,