All of lore.kernel.org
 help / color / mirror / Atom feed
From: Santosh Puranik <santosh.puranik.ibm@gmail.com>
To: Jeremy Kerr <jk@codeconstruct.com.au>,
	openbmc@lists.ozlabs.org, joel@jms.id.au,
	andrew@codeconstruct.com.au
Subject: Re: [PATCH linux dev-6.6 3/3] net: mctp: usb: Port for kernel 6.6
Date: Mon, 28 Apr 2025 19:13:15 +0530	[thread overview]
Message-ID: <9435ce2e-b7a2-415a-a67b-596ddfd7bf61@gmail.com> (raw)
In-Reply-To: <b8064801a2f4c50edaf1f69f414751794df87817.camel@codeconstruct.com.au>

Hi Jeremy,

Thank you for the review.

On 28/04/25 7:13 AM, Jeremy Kerr wrote:
> Hi Santosh,
> 
>> --- a/drivers/net/mctp/mctp-usb.c
>> +++ b/drivers/net/mctp/mctp-usb.c
>> @@ -48,16 +48,17 @@ static void mctp_usb_out_complete(struct urb *urb)
>>          case -ECONNRESET:
>>          case -ESHUTDOWN:
>>          case -EPROTO:
>> -               dev_dstats_tx_dropped(netdev);
>> +        netdev->stats.tx_dropped++;
> 
> Some weird indenting happening here (and with most of the other
> additions too).

Will fix in v2. Thanks.

> 
> If we don't want to use dstats, we should also remove
> 
>      dev->pcpu_stat_type = NETDEV_PCPU_STAT_DSTATS;
> 
> Have you checked that the stats look correct in your backport?

Yes, they did, for ex:

```
mctpusb0  Link encap:UNSPEC  HWaddr 
00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
           UP RUNNING NOARP  MTU:68  Metric:1
           RX packets:1 errors:0 dropped:0 overruns:0 frame:0
           TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
           collisions:0 txqueuelen:1000
           RX bytes:11 (11.0 B)  TX bytes:13 (13.0 B)
```
I will remove the stat_type assignment and re-run the test before 
submitting v2.

> 
>> @@ -340,7 +342,7 @@ static int mctp_usb_probe(struct usb_interface *intf,
>>   
>>          INIT_DELAYED_WORK(&dev->rx_retry_work, mctp_usb_rx_retry_work);
>>   
>> -       rc = mctp_register_netdev(netdev, NULL, MCTP_PHYS_BINDING_USB);
>> +       rc = mctp_register_netdev(netdev, NULL);
>>          if (rc)
>>                  goto err_free_urbs;
> 
> Alternatively, we could consider backporting 580db513b4a9 ("net: mctp:
> Expose transport binding identifier via IFLA attribute") too. This would
> be user-visible, as we would now have an new IFLA_MCTP_PHYS_BINDING
> attribute on netlink update messages, but that should be entirely
> backward-compatible for applications.

Ack. Please Let me know if you have a preference.

> 
> Cheers,
> 
> 
> Jeremy



  reply	other threads:[~2025-04-28 13:43 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-27 15:30 [PATCH linux dev-6.6 0/3] Backport MCTP Over USB Binding Santosh Puranik
2025-04-27 15:30 ` [PATCH linux dev-6.6 1/3] usb: Add base USB MCTP definitions Santosh Puranik
2025-04-27 15:30 ` [PATCH linux dev-6.6 2/3] net: mctp: Add MCTP USB transport driver Santosh Puranik
2025-04-27 15:30 ` [PATCH linux dev-6.6 3/3] net: mctp: usb: Port for kernel 6.6 Santosh Puranik
2025-04-28  1:43   ` Jeremy Kerr
2025-04-28 13:43     ` Santosh Puranik [this message]
2025-04-28  1:43 ` [PATCH linux dev-6.6 0/3] Backport MCTP Over USB Binding Jeremy Kerr
2025-04-28 13:45   ` Santosh Puranik
2025-04-30  3:58   ` Andrew Jeffery
2025-05-06  7:11     ` Andrew Jeffery
2025-05-07 17:41       ` Santosh Puranik

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=9435ce2e-b7a2-415a-a67b-596ddfd7bf61@gmail.com \
    --to=santosh.puranik.ibm@gmail.com \
    --cc=andrew@codeconstruct.com.au \
    --cc=jk@codeconstruct.com.au \
    --cc=joel@jms.id.au \
    --cc=openbmc@lists.ozlabs.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.