From: "Niklas Söderlund" <niklas.soderlund+renesas@ragnatech.se>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>, Andrew Lunn <andrew@lunn.ch>,
netdev@vger.kernel.org, linux-renesas-soc@vger.kernel.org
Subject: Re: [net-next,v6] net: ethernet: rtsn: Add support for Renesas Ethernet-TSN
Date: Wed, 12 Jun 2024 13:45:26 +0200 [thread overview]
Message-ID: <20240612114526.GF382677@ragnatech.se> (raw)
In-Reply-To: <20240611195616.2e71c334@kernel.org>
Hi Jakub,
Thanks for your review.
I will address all comments. I had already posted a v7 of this prior to
your comments addressing a silly build issue I failed to catch. I have
mark v7 as change requested in patchwork.
I do have one question.
On 2024-06-11 19:56:16 -0700, Jakub Kicinski wrote:
> > + netdev_info(ndev, "MAC address %pM\n", ndev->dev_addr);
>
> That's fairly unusual, why print the MAC address to logs?
Renesas net drivers print the MAC address in probe,
* RAVB
netdev_info(ndev, "Base address at %#x, %pM, IRQ %d.\n",
(u32)ndev->base_addr, ndev->dev_addr, ndev->irq);
* SH_ETH
netdev_info(ndev, "Base address at 0x%x, %pM, IRQ %d.\n",
(u32)ndev->base_addr, ndev->dev_addr, ndev->irq);
* RENESAS_ETHER_SWITCH
rswitch_for_each_enabled_port(priv, i)
netdev_info(priv->rdev[i]->ndev, "MAC address %pM\n",
priv->rdev[i]->ndev->dev_addr);
I have no strong opinion on if this is good or bad, but I do think they
all shall behave the same. What do you think is the best way forward,
keep this behavior in this new RTSN driver or remove the print from the
old drivers?
--
Kind Regards,
Niklas Söderlund
next prev parent reply other threads:[~2024-06-12 11:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-10 13:59 [net-next,v6] net: ethernet: rtsn: Add support for Renesas Ethernet-TSN Niklas Söderlund
2024-06-12 2:56 ` Jakub Kicinski
2024-06-12 11:45 ` Niklas Söderlund [this message]
2024-06-12 21:47 ` Jakub Kicinski
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=20240612114526.GF382677@ragnatech.se \
--to=niklas.soderlund+renesas@ragnatech.se \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=yoshihiro.shimoda.uh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).