From: Oliver Neukum <oneukum@suse.com>
To: Ethan Nelson-Moore <enelsonmoore@gmail.com>
Cc: netdev@vger.kernel.org, linux-usb@vger.kernel.org,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net-next 3/3] net: usb: kaweth: remove eth_addr_t typedef and bcast_addr definition
Date: Tue, 27 Jan 2026 10:23:51 +0100 [thread overview]
Message-ID: <314effcc-5bf2-47c5-9757-aafd5b47fe65@suse.com> (raw)
In-Reply-To: <CADkSEUjgRrC9eAQYOkaErd7wyXKkUs7+dG+Q1jz7VbqF+zxwuw@mail.gmail.com>
On 27.01.26 05:38, Ethan Nelson-Moore wrote:
> Hope that helps you get a sense of how much these drivers are being used.
Hi,
yes I am aware of this. Yet there is no point in breaking
existing setups. I would prefer this driver to get only
clear fixes and adaptions to changes in API that are absolutely
necessary.
Regards
Oliver
next prev parent reply other threads:[~2026-01-27 9:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-25 8:34 [PATCH net-next 0/3] net: usb: adhere to style by removing typedefs Ethan Nelson-Moore
2026-01-25 8:34 ` [PATCH net-next 1/3] net: usb: rtl8150: remove rtl8150_t typedef for struct rtl8150 Ethan Nelson-Moore
2026-01-25 16:40 ` Andrew Lunn
2026-01-25 21:49 ` Ethan Nelson-Moore
2026-01-25 8:34 ` [PATCH net-next 2/3] net: usb: pegasus: remove pegasus_t typedef for struct pegasus Ethan Nelson-Moore
2026-01-25 8:34 ` [PATCH net-next 3/3] net: usb: kaweth: remove eth_addr_t typedef and bcast_addr definition Ethan Nelson-Moore
2026-01-26 11:49 ` Oliver Neukum
2026-01-27 4:38 ` Ethan Nelson-Moore
2026-01-27 9:23 ` Oliver Neukum [this message]
2026-01-29 3:41 ` Ethan Nelson-Moore
2026-01-29 9:13 ` Oliver Neukum
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=314effcc-5bf2-47c5-9757-aafd5b47fe65@suse.com \
--to=oneukum@suse.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=enelsonmoore@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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