From: Andrew Lunn <andrew@lunn.ch>
To: Oliver Neukum <oneukum@suse.com>
Cc: hayeswang@realtek.com, grundler@chromium.org,
davem@davemloft.net, netdev@vger.kernel.org,
linux-usb@vger.kernel.org
Subject: Re: [PATCHv2 0/3] usbnet: speed reporting for devices without MDIO
Date: Fri, 22 Jan 2021 02:29:01 +0100 [thread overview]
Message-ID: <YAoqXZJVhRDiRI+9@lunn.ch> (raw)
In-Reply-To: <20210121125731.19425-1-oneukum@suse.com>
On Thu, Jan 21, 2021 at 01:57:28PM +0100, Oliver Neukum wrote:
> This series introduces support for USB network devices that report
> speed as a part of their protocol, not emulating an MII to be accessed
> over MDIO.
>
> v2: adjusted to recent changes
Hi Oliver
Please give more details what actually changed. Does this mean you
just rebased it on net-next? Or have you made real changes?
The discussion with v1 suggested that this framework should also be
used by anything which gets notified in CDC style. So i was expecting
to see cdc_ether.c also use this.
Andrew
next prev parent reply other threads:[~2021-01-22 1:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-21 12:57 [PATCHv2 0/3] usbnet: speed reporting for devices without MDIO Oliver Neukum
2021-01-21 12:57 ` [PATCHv2 1/3] usbnet: specify naming of usbnet_set/get_link_ksettings Oliver Neukum
2021-01-22 1:10 ` Andrew Lunn
2021-01-26 9:42 ` Oliver Neukum
2021-01-26 13:34 ` Andrew Lunn
2021-01-21 12:57 ` [PATCHv2 2/3] usbnet: add method for reporting speed without MDIO Oliver Neukum
2021-01-22 1:35 ` Grant Grundler
2021-01-22 2:56 ` Grant Grundler
2021-01-21 12:57 ` [PATCHv2 3/3] CDC-NCM: record speed in status method Oliver Neukum
2021-01-22 3:02 ` Grant Grundler
2021-01-22 1:29 ` Andrew Lunn [this message]
2021-01-22 2:10 ` [PATCHv2 0/3] usbnet: speed reporting for devices without MDIO Grant Grundler
2021-02-09 23:47 ` Grant Grundler
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=YAoqXZJVhRDiRI+9@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=grundler@chromium.org \
--cc=hayeswang@realtek.com \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=oneukum@suse.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).