| Message ID | 20190919000946.158454-1-mka@chromium.org (mailing list archive) |
|---|---|
| State | Not Applicable, archived |
| Headers | show |
| Series | devfreq: Make log message more explicit when devfreq device already exists | expand |
>Before creating a new devfreq device devfreq_add_device() checks >if there is already a devfreq dev associated with the requesting >device (parent). If that's the case the function rejects to create >another devfreq dev for that parent and logs an error. The error >message is very unspecific, make it a bit more explicit. > >Signed-off-by: Matthias Kaehlcke <mka@chromium.org> >--- > drivers/devfreq/devfreq.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > >diff --git a/drivers/devfreq/devfreq.c b/drivers/devfreq/devfreq.c >index ab22bf8a12d6..0e2dd734ab58 100644 >--- a/drivers/devfreq/devfreq.c >+++ b/drivers/devfreq/devfreq.c >@@ -625,7 +625,7 @@ struct devfreq *devfreq_add_device(struct device *dev, > devfreq = find_device_devfreq(dev); > mutex_unlock(&devfreq_list_lock); > if (!IS_ERR(devfreq)) { >- dev_err(dev, "%s: Unable to create devfreq for the device.\n", >+ dev_err(dev, "%s: devfreq device already exists!\n", Yes, this is more helpful! Thanks! Acked-by: MyungJoo Ham <myungjoo.ham@samsung.com>
Hi, On 19. 9. 19. 오전 9:09, Matthias Kaehlcke wrote: > Before creating a new devfreq device devfreq_add_device() checks > if there is already a devfreq dev associated with the requesting > device (parent). If that's the case the function rejects to create > another devfreq dev for that parent and logs an error. The error > message is very unspecific, make it a bit more explicit. > > Signed-off-by: Matthias Kaehlcke <mka@chromium.org> > --- > drivers/devfreq/devfreq.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/devfreq/devfreq.c b/drivers/devfreq/devfreq.c > index ab22bf8a12d6..0e2dd734ab58 100644 > --- a/drivers/devfreq/devfreq.c > +++ b/drivers/devfreq/devfreq.c > @@ -625,7 +625,7 @@ struct devfreq *devfreq_add_device(struct device *dev, > devfreq = find_device_devfreq(dev); > mutex_unlock(&devfreq_list_lock); > if (!IS_ERR(devfreq)) { > - dev_err(dev, "%s: Unable to create devfreq for the device.\n", > + dev_err(dev, "%s: devfreq device already exists!\n", Looks good to me. But After edited the log message, you can make it on one line because the length is not over 80 char. You can change it for the readability as following: if (!IS_ERR(devfreq)) { - dev_err(dev, "%s: Unable to create devfreq for the device.\n", - __func__); + dev_err(dev, "%s: devfreq device already exists.\n", __func__); If you agree my comment, you can feel free to add my tag: Reviewed-by: Chanwoo Choi <cw00.choi@samsung.com> > __func__); > err = -EINVAL; > goto err_out; >
diff --git a/drivers/devfreq/devfreq.c b/drivers/devfreq/devfreq.c index ab22bf8a12d6..0e2dd734ab58 100644 --- a/drivers/devfreq/devfreq.c +++ b/drivers/devfreq/devfreq.c @@ -625,7 +625,7 @@ struct devfreq *devfreq_add_device(struct device *dev, devfreq = find_device_devfreq(dev); mutex_unlock(&devfreq_list_lock); if (!IS_ERR(devfreq)) { - dev_err(dev, "%s: Unable to create devfreq for the device.\n", + dev_err(dev, "%s: devfreq device already exists!\n", __func__); err = -EINVAL; goto err_out;
Before creating a new devfreq device devfreq_add_device() checks if there is already a devfreq dev associated with the requesting device (parent). If that's the case the function rejects to create another devfreq dev for that parent and logs an error. The error message is very unspecific, make it a bit more explicit. Signed-off-by: Matthias Kaehlcke <mka@chromium.org> --- drivers/devfreq/devfreq.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)