From: Greg KH <greg@kroah.com>
To: yicongsrfy@163.com
Cc: oneukum@suse.com, andrew+netdev@lunn.ch, davem@davemloft.net,
netdev@vger.kernel.org, linux-usb@vger.kernel.org,
Yi Cong <yicong@kylinos.cn>
Subject: Re: [PATCH] net: cdc_ncm: Fix spelling mistakes
Date: Tue, 22 Jul 2025 07:46:34 +0200 [thread overview]
Message-ID: <2025072210-spherical-grating-a779@gregkh> (raw)
In-Reply-To: <20250722023259.1228935-1-yicongsrfy@163.com>
On Tue, Jul 22, 2025 at 10:32:59AM +0800, yicongsrfy@163.com wrote:
> From: Yi Cong <yicong@kylinos.cn>
>
> According to the Universal Serial Bus Class Definitions for
> Communications Devices v1.2, in chapter 6.3.3 table-21:
> DLBitRate(downlink bit rate) seems like spelling error.
>
> Signed-off-by: Yi Cong <yicong@kylinos.cn>
> ---
> drivers/net/usb/cdc_ncm.c | 2 +-
> include/uapi/linux/usb/cdc.h | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/net/usb/cdc_ncm.c b/drivers/net/usb/cdc_ncm.c
> index 34e82f1e37d9..057ad1cf0820 100644
> --- a/drivers/net/usb/cdc_ncm.c
> +++ b/drivers/net/usb/cdc_ncm.c
> @@ -1847,7 +1847,7 @@ cdc_ncm_speed_change(struct usbnet *dev,
> struct usb_cdc_speed_change *data)
> {
> /* RTL8156 shipped before 2021 sends notification about every 32ms. */
> - dev->rx_speed = le32_to_cpu(data->DLBitRRate);
> + dev->rx_speed = le32_to_cpu(data->DLBitRate);
> dev->tx_speed = le32_to_cpu(data->ULBitRate);
> }
>
> diff --git a/include/uapi/linux/usb/cdc.h b/include/uapi/linux/usb/cdc.h
> index 1924cf665448..f528c8e0a04e 100644
> --- a/include/uapi/linux/usb/cdc.h
> +++ b/include/uapi/linux/usb/cdc.h
> @@ -316,7 +316,7 @@ struct usb_cdc_notification {
> #define USB_CDC_SERIAL_STATE_OVERRUN (1 << 6)
>
> struct usb_cdc_speed_change {
> - __le32 DLBitRRate; /* contains the downlink bit rate (IN pipe) */
> + __le32 DLBitRate; /* contains the downlink bit rate (IN pipe) */
> __le32 ULBitRate; /* contains the uplink bit rate (OUT pipe) */
> } __attribute__ ((packed));
You are changing a structure that userspace sees. How did you verify
that this is not going to break any existing code out there?
thanks,
greg k-h
next prev parent reply other threads:[~2025-07-22 5:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-22 2:32 [PATCH] net: cdc_ncm: Fix spelling mistakes yicongsrfy
2025-07-22 5:46 ` Greg KH [this message]
2025-07-22 6:51 ` yicongsrfy
2025-07-22 6:56 ` Greg KH
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=2025072210-spherical-grating-a779@gregkh \
--to=greg@kroah.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oneukum@suse.com \
--cc=yicong@kylinos.cn \
--cc=yicongsrfy@163.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