Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux

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 <rafael.j.wysocki@intel.com>
Signed-off-by: Thierry Reding <treding@nvidia.com>
Link: https://lore.kernel.org/r/20201127104630.1839171-1-thierry.reding@gmail.com
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>

authored by

Thierry Reding and committed by
Greg Kroah-Hartman
d475f8ea 5b6164d3

+2 -2
+2 -2
drivers/base/core.c
··· 561 561 * with runtime PM. First, setting the DL_FLAG_PM_RUNTIME flag will cause the 562 562 * runtime PM framework to take the link into account. Second, if the 563 563 * DL_FLAG_RPM_ACTIVE flag is set in addition to it, the supplier devices will 564 - * be forced into the active metastate and reference-counted upon the creation 564 + * be forced into the active meta state and reference-counted upon the creation 565 565 * of the link. If DL_FLAG_PM_RUNTIME is not set, DL_FLAG_RPM_ACTIVE will be 566 566 * ignored. 567 567 * ··· 584 584 * Also, if DL_FLAG_STATELESS, DL_FLAG_AUTOREMOVE_CONSUMER and 585 585 * DL_FLAG_AUTOREMOVE_SUPPLIER are not set in @flags (that is, a persistent 586 586 * managed device link is being added), the DL_FLAG_AUTOPROBE_CONSUMER flag can 587 - * be used to request the driver core to automaticall probe for a consmer 587 + * be used to request the driver core to automatically probe for a consumer 588 588 * driver after successfully binding a driver to the supplier device. 589 589 * 590 590 * The combination of DL_FLAG_STATELESS and one of DL_FLAG_AUTOREMOVE_CONSUMER,