From: Lee Jones <lee.jones@linaro.org>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org,
Julia Lawall <julia.lawall@lip6.fr>
Subject: Re: [PATCH v4] mfd: dm355evm_msp: Refactoring for add_child()
Date: Tue, 09 Aug 2016 09:30:22 +0000 [thread overview]
Message-ID: <20160809093022.GU5243@dell> (raw)
In-Reply-To: <0a2ef320-a95a-2611-2554-a2a83838fb9b@users.sourceforge.net>
On Mon, 08 Aug 2016, SF Markus Elfring wrote:
> >> v4: Further feedback was integrated into this message.
> >
> > This is not a good change-log. What actually changed?
>
> Which kind of information would you find more useful in this case?
That's for you to tell me surely?
If I wanted to know what changed, I would normally look at the patch
change-log. But the change-log in this patch says "I did some
stuff". What stuff did you change? Which review comments did you
tend to?
>
> >> @@ -222,19 +222,20 @@ static struct device *add_child(struct i2c_client *client, const char *name,
> >> status = platform_device_add_resources(pdev, &r, 1);
> >> if (status < 0) {
> >> dev_dbg(&pdev->dev, "can't add irq\n");
> >> - goto err;
> >> + goto put_device;
> >> }
> >> }
> >>
> >> status = platform_device_add(pdev);
> >> + if (status)
> >> + goto put_device;
> >>
> >> -err:
> >> - if (status < 0) {
> >> - platform_device_put(pdev);
> >> - dev_err(&client->dev, "can't add %s dev\n", name);
> >> - return ERR_PTR(status);
> >> - }
> >> return &pdev->dev;
> >> +
> >> +put_device:
> >> + platform_device_put(pdev);
> >> + dev_err(&client->dev, "failed to add device %s\n", name);
> >
> > ... and remove this line.
>
> -Do you really want that this error message should be deleted?
>
> How does this response fit to your request to introduce such a message
> for the function "add_numbered_child" (on 2016-06-08)?
> https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1162299.html
> https://lkml.org/lkml/2016/6/8/467
You've lost the context. The "..." is meant to intimate that it
follows on from a previous comment. In this case:
> > status = platform_device_add_data(pdev, pdata, pdata_len);
> > if (status < 0) {
> > dev_dbg(&pdev->dev, "can't add platform_data\n");
>
> Please take the opportunity to convert these to dev_err()s.
So, convert the specific dev_dbg() calls to dev_err() and remove the
contentless one at the bottom.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
--
To unsubscribe from this list: send the line "unsubscribe kernel-janitors" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Lee Jones <lee.jones@linaro.org>
To: SF Markus Elfring <elfring@users.sourceforge.net>
Cc: LKML <linux-kernel@vger.kernel.org>,
kernel-janitors@vger.kernel.org,
Julia Lawall <julia.lawall@lip6.fr>
Subject: Re: [PATCH v4] mfd: dm355evm_msp: Refactoring for add_child()
Date: Tue, 9 Aug 2016 10:30:22 +0100 [thread overview]
Message-ID: <20160809093022.GU5243@dell> (raw)
In-Reply-To: <0a2ef320-a95a-2611-2554-a2a83838fb9b@users.sourceforge.net>
On Mon, 08 Aug 2016, SF Markus Elfring wrote:
> >> v4: Further feedback was integrated into this message.
> >
> > This is not a good change-log. What actually changed?
>
> Which kind of information would you find more useful in this case?
That's for you to tell me surely?
If I wanted to know what changed, I would normally look at the patch
change-log. But the change-log in this patch says "I did some
stuff". What stuff did you change? Which review comments did you
tend to?
>
> >> @@ -222,19 +222,20 @@ static struct device *add_child(struct i2c_client *client, const char *name,
> >> status = platform_device_add_resources(pdev, &r, 1);
> >> if (status < 0) {
> >> dev_dbg(&pdev->dev, "can't add irq\n");
> >> - goto err;
> >> + goto put_device;
> >> }
> >> }
> >>
> >> status = platform_device_add(pdev);
> >> + if (status)
> >> + goto put_device;
> >>
> >> -err:
> >> - if (status < 0) {
> >> - platform_device_put(pdev);
> >> - dev_err(&client->dev, "can't add %s dev\n", name);
> >> - return ERR_PTR(status);
> >> - }
> >> return &pdev->dev;
> >> +
> >> +put_device:
> >> + platform_device_put(pdev);
> >> + dev_err(&client->dev, "failed to add device %s\n", name);
> >
> > ... and remove this line.
>
> -Do you really want that this error message should be deleted?
>
> How does this response fit to your request to introduce such a message
> for the function "add_numbered_child" (on 2016-06-08)?
> https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1162299.html
> https://lkml.org/lkml/2016/6/8/467
You've lost the context. The "..." is meant to intimate that it
follows on from a previous comment. In this case:
> > status = platform_device_add_data(pdev, pdata, pdata_len);
> > if (status < 0) {
> > dev_dbg(&pdev->dev, "can't add platform_data\n");
>
> Please take the opportunity to convert these to dev_err()s.
So, convert the specific dev_dbg() calls to dev_err() and remove the
contentless one at the bottom.
--
Lee Jones
Linaro STMicroelectronics Landing Team Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
next prev parent reply other threads:[~2016-08-09 9:30 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-01 17:29 [PATCH v4] mfd: dm355evm_msp: Refactoring for add_child() SF Markus Elfring
2016-07-01 17:29 ` SF Markus Elfring
2016-08-05 7:55 ` Lee Jones
2016-08-05 7:55 ` Lee Jones
2016-08-08 11:36 ` SF Markus Elfring
2016-08-08 11:36 ` SF Markus Elfring
2016-08-09 9:30 ` Lee Jones [this message]
2016-08-09 9:30 ` Lee Jones
2016-08-09 9:56 ` SF Markus Elfring
2016-08-09 9:56 ` SF Markus Elfring
2016-08-09 15:36 ` Lee Jones
2016-08-09 15:36 ` Lee Jones
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160809093022.GU5243@dell \
--to=lee.jones@linaro.org \
--cc=elfring@users.sourceforge.net \
--cc=julia.lawall@lip6.fr \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.