public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Oliver Neukum <oneukum@suse.com>
To: "Bjørn Mork" <bjorn@mork.no>
Cc: netdev@vger.kernel.org, hayeswang@realtek.com, o.rempel@pengutronix.de
Subject: Re: [RFC net-next 1/3] net: usb: divorce private data and cdc state in usbnet
Date: Tue, 10 Feb 2026 18:11:56 +0100	[thread overview]
Message-ID: <98556af0-cb77-4f8b-a8f8-a121a66a8a76@suse.com> (raw)
In-Reply-To: <87ikc4mumr.fsf@miraculix.mork.no>

Hi,

On 10.02.26 17:27, Bjørn Mork wrote:
> Oliver Neukum <oneukum@suse.com> writes:
> 
  
> But I don't understand why you make struct cdc_state special.  That's
> just confusing.

Because technically it is a layering violation to put cdc stuff
into usbnet. I want to do so that I can remove the exported symbols
from the cdc_X drivers and put them cleanly into usbnet.
That is the medium term plan.

> I know I intentionally made the "control" and "data" fields of
> "struct qmi_wwan_state" position and name compatible with
> "struct cdc_state". Maybe not very important.  But adds to the
> confusion if we end up with a double set of those fields.
> 
> Or should the qmi_wwan driver split out the
>          struct usb_interface            *control;
>          struct usb_interface            *data;
> 
> part of its private data and put those into "cdc", allowing us to reduce
> "struct qmi_wwan_state" from 5 to 3 longs?  I don't think that's a very
> good idea...

Well, QMI is not CDC. No use pretending.
But we could put them into struct usbnet as primary and secondary

	Regards
		Oliver


  reply	other threads:[~2026-02-10 17:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-10 15:11 [RFC net-next 0/3] cleanup of usbnet descriptor allocation Oliver Neukum
2026-02-10 15:11 ` [RFC net-next 1/3] net: usb: divorce private data and cdc state in usbnet Oliver Neukum
2026-02-10 16:27   ` Bjørn Mork
2026-02-10 17:11     ` Oliver Neukum [this message]
2026-02-17 18:23   ` Andrew Lunn
2026-02-18  9:53     ` Oliver Neukum
2026-02-17 18:31   ` Andrew Lunn
2026-02-10 15:11 ` [RFC net-next 2/3] net: usb: usbnet: switch to dynamic allocation of private data Oliver Neukum
2026-02-17 18:47   ` Andrew Lunn
2026-02-18 10:06     ` Oliver Neukum
2026-02-18 14:01       ` Andrew Lunn
2026-02-19  9:07         ` Oliver Neukum
2026-02-10 15:11 ` [RFC net-next 3/3] net: usb: usbnet: remove driver_priv 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=98556af0-cb77-4f8b-a8f8-a121a66a8a76@suse.com \
    --to=oneukum@suse.com \
    --cc=bjorn@mork.no \
    --cc=hayeswang@realtek.com \
    --cc=netdev@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    /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