On Wed, May 27, 2015 at 12:00 AM, Sriram Dash <dash.sri...@gmail.com> wrote: > From: dashsriram <dash.sri...@gmail.com> > > Fixed a typo error in the file > > Signed-off-by: Sriram Dash <dash.sri...@gmail.com> > --- > drivers/base/power/opp.c | 6 +++--- > 1 file changed, 3 insertions(+), 3 deletions(-) > > diff --git a/drivers/base/power/opp.c b/drivers/base/power/opp.c > index 677fb28..300941b 100644 > --- a/drivers/base/power/opp.c > +++ b/drivers/base/power/opp.c > @@ -675,7 +675,7 @@ EXPORT_SYMBOL_GPL(dev_pm_opp_remove); > * share a common logic which is isolated here. > * > * Return: -EINVAL for bad pointers, -ENOMEM if no memory available for the > - * copy operation, returns 0 if no modifcation was done OR modification was > + * copy operation, returns 0 if no modification was done OR modification was > * successful. > * > * Locking: The internal device_opp and opp structures are RCU protected. > @@ -763,7 +763,7 @@ unlock: > * mutex locking or synchronize_rcu() blocking calls cannot be used. > * > * Return: -EINVAL for bad pointers, -ENOMEM if no memory available for the > - * copy operation, returns 0 if no modifcation was done OR modification was > + * copy operation, returns 0 if no modification was done OR modification was > * successful. > */ > int dev_pm_opp_enable(struct device *dev, unsigned long freq) > @@ -789,7 +789,7 @@ EXPORT_SYMBOL_GPL(dev_pm_opp_enable); > * mutex locking or synchronize_rcu() blocking calls cannot be used. > * > * Return: -EINVAL for bad pointers, -ENOMEM if no memory available for the > - * copy operation, returns 0 if no modifcation was done OR modification was > + * copy operation, returns 0 if no modification was done OR modification was > * successful. > */ > int dev_pm_opp_disable(struct device *dev, unsigned long freq)
Reviewed-by: Viresh Kumar <viresh.ku...@linaro.org> -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
