From: Sebastian Frias <sf84@laposte.net>
To: "Måns Rullgård" <mans@mansr.com>
Cc: "David S. Miller" <davem@davemloft.net>,
netdev@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
mason <slash.tmp@free.fr>
Subject: Re: [PATCH v3] net: ethernet: support "fixed-link" DT node on nb8800 driver
Date: Fri, 05 Feb 2016 16:20:58 +0100 [thread overview]
Message-ID: <56B4BDDA.9010708@laposte.net> (raw)
In-Reply-To: <yw1xfux7gpol.fsf@unicorn.mansr.com>
On 02/05/2016 04:08 PM, Måns Rullgård wrote:
> Sebastian Frias <sf84@laposte.net> writes:
>
>> On 02/05/2016 03:34 PM, Måns Rullgård wrote:
>>> Sebastian Frias <sf84@laposte.net> writes:
>>>
>>>> Signed-off-by: Sebastian Frias <sf84@laposte.net>
>>>
>>> Please change the subject to something like "net: ethernet: nb8800:
>>> support fixed-link DT node" and add a comment body.
>>
>> The subject is pretty explicit for such a simple patch, what else
>> could I add that wouldn't be unnecessary chat?
>
> It's customary to include a description body even if it's little more
> than a restatement of the subject. Also, while the subject usually only
> says _what_ the patch does, the body should additionally state _why_ it
> is needed.
I understand, but _why_ it is needed is also obvious in this case; I
mean, without the patch "fixed-link" cannot be used.
Other patches may not be as obvious/simple and thus justify and require
more details.
Anyway, I added "Properly handles the case where the PHY is not connected
to the real MDIO bus" would that be ok?
>
>>>> ---
>>>> drivers/net/ethernet/aurora/nb8800.c | 14 +++++++++++++-
>>>> 1 file changed, 13 insertions(+), 1 deletion(-)
>>>>
>>>> diff --git a/drivers/net/ethernet/aurora/nb8800.c
>>>> b/drivers/net/ethernet/aurora/nb8800.c
>>>> index ecc4a33..e1fb071 100644
>>>> --- a/drivers/net/ethernet/aurora/nb8800.c
>>>> +++ b/drivers/net/ethernet/aurora/nb8800.c
>>>> @@ -1460,7 +1460,19 @@ static int nb8800_probe(struct platform_device *pdev)
>>>> goto err_disable_clk;
>>>> }
>>>>
>>>> - priv->phy_node = of_parse_phandle(pdev->dev.of_node, "phy-handle", 0);
>>>> + if (of_phy_is_fixed_link(pdev->dev.of_node)) {
>>>> + ret = of_phy_register_fixed_link(pdev->dev.of_node);
>>>> + if (ret < 0) {
>>>> + dev_err(&pdev->dev, "bad fixed-link spec\n");
>>>> + goto err_free_bus;
>>>> + }
>>>> + priv->phy_node = of_node_get(pdev->dev.of_node);
>>>> + }
>>>> +
>>>> + if (!priv->phy_node)
>>>> + priv->phy_node = of_parse_phandle(pdev->dev.of_node,
>>>> + "phy-handle", 0);
>>>> +
>>>> if (!priv->phy_node) {
>>>> dev_err(&pdev->dev, "no PHY specified\n");
>>>> ret = -ENODEV;
>>>> --
>>>> 2.1.4
>>>
>
next prev parent reply other threads:[~2016-02-05 15:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-05 13:31 [PATCH] net: ethernet: support "fixed-link" DT node on nb8800 driver Sebastian Frias
2016-02-05 13:39 ` Måns Rullgård
2016-02-05 13:49 ` [PATCH v2] net: ethernet: support "fixed-link" DT key/node " Sebastian Frias
2016-02-05 13:58 ` Måns Rullgård
2016-02-05 14:08 ` Sebastian Frias
2016-02-05 14:13 ` Måns Rullgård
2016-02-05 14:22 ` [PATCH v3] net: ethernet: support "fixed-link" DT node " Sebastian Frias
2016-02-05 14:34 ` Måns Rullgård
2016-02-05 14:56 ` Sebastian Frias
2016-02-05 15:08 ` Måns Rullgård
2016-02-05 15:20 ` Sebastian Frias [this message]
2016-02-05 15:26 ` Måns Rullgård
2016-02-08 10:23 ` [PATCH v5] net: ethernet: nb8800: support fixed-link DT node Sebastian Frias
2016-02-08 13:19 ` Måns Rullgård
2016-02-16 20:04 ` David Miller
2016-02-22 12:39 ` Mason
2016-02-08 10:34 ` [PATCH v3] net: ethernet: support "fixed-link" DT node on nb8800 driver Sebastian Frias
2016-02-08 13:37 ` Måns Rullgård
2016-02-08 14:11 ` Mason
2016-02-08 14:38 ` Sebastian Frias
2016-02-08 14:44 ` Måns Rullgård
2016-02-08 14:32 ` Sebastian Frias
2016-02-08 14:50 ` Måns Rullgård
2016-02-05 14:56 ` [PATCH v4] net: ethernet: nb8800: support fixed-link DT node Sebastian Frias
2016-02-05 15:57 ` [PATCH] net: ethernet: support "fixed-link" DT node on nb8800 driver Andy Shevchenko
2016-02-05 15:58 ` Måns Rullgård
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=56B4BDDA.9010708@laposte.net \
--to=sf84@laposte.net \
--cc=davem@davemloft.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mans@mansr.com \
--cc=netdev@vger.kernel.org \
--cc=slash.tmp@free.fr \
/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.