From: Ravi Gunasekaran <r-gunasekaran@ti.com>
To: Lukasz Majewski <lukma@denx.de>,
Oleksij Rempel <o.rempel@pengutronix.de>
Cc: Eric Dumazet <edumazet@google.com>,
Vladimir Oltean <olteanv@gmail.com>,
"David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>, <netdev@vger.kernel.org>,
<Tristram.Ha@microchip.com>,
"Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
Paolo Abeni <pabeni@redhat.com>,
"Nikita Zhandarovich" <n.zhandarovich@fintech.ru>,
Murali Karicheri <m-karicheri2@ti.com>,
Ziyang Xuan <william.xuanziyang@huawei.com>,
<linux-kernel@vger.kernel.org>,
Ravi Gunasekaran <r-gunasekaran@ti.com>
Subject: Re: [PATCH] net: hsr: Use full string description when opening HSR network device
Date: Mon, 4 Mar 2024 16:02:48 +0530 [thread overview]
Message-ID: <8d92dcbb-828d-17f4-d199-c625505e7b0c@ti.com> (raw)
In-Reply-To: <20240304093220.4183179-1-lukma@denx.de>
On 3/4/24 3:02 PM, Lukasz Majewski wrote:
> Up till now only single character ('A' or 'B') was used to provide
> information of HSR slave network device status.
>
> As it is also possible and valid, that Interlink network device may
> be supported as well, the description must be more verbose. As a result
> the full string description is now used.
>
> Signed-off-by: Lukasz Majewski <lukma@denx.de>
> ---
> net/hsr/hsr_device.c | 13 ++++++-------
> 1 file changed, 6 insertions(+), 7 deletions(-)
>
> diff --git a/net/hsr/hsr_device.c b/net/hsr/hsr_device.c
> index 9d71b66183da..9a60489fba96 100644
> --- a/net/hsr/hsr_device.c
> +++ b/net/hsr/hsr_device.c
> @@ -142,30 +142,29 @@ static int hsr_dev_open(struct net_device *dev)
> {
> struct hsr_priv *hsr;
> struct hsr_port *port;
> - char designation;
> + char *designation = NULL;
>
> hsr = netdev_priv(dev);
> - designation = '\0';
>
> hsr_for_each_port(hsr, port) {
> if (port->type == HSR_PT_MASTER)
> continue;
> switch (port->type) {
> case HSR_PT_SLAVE_A:
> - designation = 'A';
> + designation = "Slave A";
"designation" is now a pointer and is being assigned value
without even allocating memory for it.
> break;
> case HSR_PT_SLAVE_B:
> - designation = 'B';
> + designation = "Slave B";
> break;
> default:
> - designation = '?';
> + designation = "Unknown";
> }
> if (!is_slave_up(port->dev))
> - netdev_warn(dev, "Slave %c (%s) is not up; please bring it up to get a fully working HSR network\n",
> + netdev_warn(dev, "%s (%s) is not up; please bring it up to get a fully working HSR network\n",
> designation, port->dev->name);
> }
>
> - if (designation == '\0')
> + if (!designation)
> netdev_warn(dev, "No slave devices configured\n");
>
> return 0;
--
Regards,
Ravi
next prev parent reply other threads:[~2024-03-04 10:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-04 9:32 [PATCH] net: hsr: Use full string description when opening HSR network device Lukasz Majewski
2024-03-04 10:32 ` Ravi Gunasekaran [this message]
2024-03-04 14:21 ` Andrew Lunn
2024-03-04 14:24 ` Andrew Lunn
2024-03-04 15:17 ` Lukasz Majewski
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=8d92dcbb-828d-17f4-d199-c625505e7b0c@ti.com \
--to=r-gunasekaran@ti.com \
--cc=Tristram.Ha@microchip.com \
--cc=bigeasy@linutronix.de \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lukma@denx.de \
--cc=m-karicheri2@ti.com \
--cc=n.zhandarovich@fintech.ru \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=william.xuanziyang@huawei.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