From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: netdev@vger.kernel.org, nobuhiro.iwamatsu.yj@renesas.com,
linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh_eth: use random MAC address if no valid one supplied
Date: Mon, 29 Apr 2013 11:43:51 +0000 [thread overview]
Message-ID: <517E5CF7.4000600@cogentembedded.com> (raw)
In-Reply-To: <1405436.hE5aNhyzLb@avalon>
Hello.
On 29-04-2013 0:29, Laurent Pinchart wrote:
>> On Renesas R-Car based development boards, although a MAC address is printed
>> on all the Ethernet port labels, U-Boot doesn't write a valid MAC address
>> to the Ether MAHR/MALR registers (there's no storage provided for the Ether
>> MAC address either), so we have to resort to using a random MAC address...
>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>> ---
>> This patch is against the 'net-next.git' repository.
>> drivers/net/ethernet/renesas/sh_eth.c | 5 +++++
>> 1 file changed, 5 insertions(+)
>> Index: net-next/drivers/net/ethernet/renesas/sh_eth.c
>> =================================>> --- net-next.orig/drivers/net/ethernet/renesas/sh_eth.c
>> +++ net-next/drivers/net/ethernet/renesas/sh_eth.c
>> @@ -2735,6 +2735,11 @@ static int sh_eth_drv_probe(struct platf
>>
>> /* read and set MAC address */
>> read_mac_address(ndev, pd->mac_addr);
>> + if (!is_valid_ether_addr(ndev->dev_addr)) {
>> + dev_warn(&pdev->dev, "no valid MAC address supplied, using "
>> + "a random one.\n");
> Breaking log messages in the middle of a line is frowned upon, more than
> exceeding the 80 characters per line (soft) limit. I think
> dev_warn(&pdev->dev,
> "no valid MAC address supplied, using a random one.\n");
> would be better.
Thanks, totally forgot about that when doing a patch, only remembered
after sending out.
WBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: netdev@vger.kernel.org, nobuhiro.iwamatsu.yj@renesas.com,
linux-sh@vger.kernel.org
Subject: Re: [PATCH] sh_eth: use random MAC address if no valid one supplied
Date: Mon, 29 Apr 2013 15:43:51 +0400 [thread overview]
Message-ID: <517E5CF7.4000600@cogentembedded.com> (raw)
In-Reply-To: <1405436.hE5aNhyzLb@avalon>
Hello.
On 29-04-2013 0:29, Laurent Pinchart wrote:
>> On Renesas R-Car based development boards, although a MAC address is printed
>> on all the Ethernet port labels, U-Boot doesn't write a valid MAC address
>> to the Ether MAHR/MALR registers (there's no storage provided for the Ether
>> MAC address either), so we have to resort to using a random MAC address...
>> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>> ---
>> This patch is against the 'net-next.git' repository.
>> drivers/net/ethernet/renesas/sh_eth.c | 5 +++++
>> 1 file changed, 5 insertions(+)
>> Index: net-next/drivers/net/ethernet/renesas/sh_eth.c
>> ===================================================================
>> --- net-next.orig/drivers/net/ethernet/renesas/sh_eth.c
>> +++ net-next/drivers/net/ethernet/renesas/sh_eth.c
>> @@ -2735,6 +2735,11 @@ static int sh_eth_drv_probe(struct platf
>>
>> /* read and set MAC address */
>> read_mac_address(ndev, pd->mac_addr);
>> + if (!is_valid_ether_addr(ndev->dev_addr)) {
>> + dev_warn(&pdev->dev, "no valid MAC address supplied, using "
>> + "a random one.\n");
> Breaking log messages in the middle of a line is frowned upon, more than
> exceeding the 80 characters per line (soft) limit. I think
> dev_warn(&pdev->dev,
> "no valid MAC address supplied, using a random one.\n");
> would be better.
Thanks, totally forgot about that when doing a patch, only remembered
after sending out.
WBR, Sergei
next prev parent reply other threads:[~2013-04-29 11:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-27 22:48 [PATCH] sh_eth: use random MAC address if no valid one supplied Sergei Shtylyov
2013-04-27 22:48 ` Sergei Shtylyov
2013-04-28 20:29 ` Laurent Pinchart
2013-04-28 20:29 ` Laurent Pinchart
2013-04-29 11:43 ` Sergei Shtylyov [this message]
2013-04-29 11:43 ` Sergei Shtylyov
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=517E5CF7.4000600@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-sh@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=nobuhiro.iwamatsu.yj@renesas.com \
/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.