From: Birger Koblitz <mail@birger-koblitz.de>
To: Jakub Kicinski <kuba@kernel.org>
Cc: Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>,
Russell King <linux@armlinux.org.uk>,
Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
linux-usb@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, Jianhui Xu <neuromoments@gmail.com>
Subject: Re: [PATCH net-next v10 06/15] ax88179_178a: Add HW support for AX179A-based chips
Date: Mon, 14 Sep 2026 07:14:46 +0200 [thread overview]
Message-ID: <2eddb9fe-22b3-4fe4-a2ab-e408e4a726e7@birger-koblitz.de> (raw)
In-Reply-To: <20260910170055.524e3c25@kernel.org>
Thanks for checking the code, Jakub!
On 9/11/26 02:00, Jakub Kicinski wrote:
> Sparse flags a number of warnings here:
>
> drivers/net/usb/ax88179a_devices.c:509:37: warning: restricted __le16 degrades to integer
> drivers/net/usb/ax88179a_devices.c:678:32: warning: incorrect type in argument 1 (different base types)
> drivers/net/usb/ax88179a_devices.c:678:32: expected restricted __le64 const [usertype] *p
> drivers/net/usb/ax88179a_devices.c:678:32: got unsigned long long [usertype] *
> drivers/net/usb/ax88179a_devices.c:705:45: warning: incorrect type in argument 1 (different base types)
> drivers/net/usb/ax88179a_devices.c:705:45: expected restricted __le64 const [usertype] *p
> drivers/net/usb/ax88179a_devices.c:705:45: got unsigned long long [usertype] *[assigned] pkt_desc_ptr
> drivers/net/usb/ax88179a_devices.c:801:22: warning: incorrect type in assignment (different base types)
> drivers/net/usb/ax88179a_devices.c:801:22: expected unsigned long long [usertype]
> drivers/net/usb/ax88179a_devices.c:801:22: got restricted __le64 [usertype]
These are indeed actual bugs and I will fix them in the next version.
Birger
next prev parent reply other threads:[~2026-09-14 5:24 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-04 17:28 [PATCH net-next v10 00/15] ax88179_178a: Add support for AX88179A-based chips Birger Koblitz
2026-09-04 17:28 ` [PATCH net-next v10 01/15] phylink: Add phylink_mac_interrupt Birger Koblitz
2026-09-04 17:28 ` [PATCH net-next v10 02/15] phylib: Add support for PHYs with broken forced mode Birger Koblitz
2026-09-04 17:28 ` [PATCH net-next v10 03/15] ax88179_178a: Fix endianness of pause watermark register Birger Koblitz
2026-09-04 17:28 ` [PATCH net-next v10 04/15] ax88179_178a: Split driver into library and device specific code Birger Koblitz
2026-09-04 17:28 ` [PATCH net-next v10 05/15] ax88179_178a: Add netdev2data() convenience function Birger Koblitz
2026-09-04 17:28 ` [PATCH net-next v10 06/15] ax88179_178a: Add HW support for AX179A-based chips Birger Koblitz
2026-09-11 0:00 ` Jakub Kicinski
2026-09-14 5:14 ` Birger Koblitz [this message]
2026-09-04 17:28 ` [PATCH net-next v10 07/15] ax88179_178a: Add EEE configuration support for AX88179A MACs Birger Koblitz
2026-09-04 17:28 ` [PATCH net-next v10 08/15] ax88179_178a: Add EEE configuration support for AX88179A PHYs Birger Koblitz
2026-09-04 17:28 ` [PATCH net-next v10 09/15] ax88179_178a: Add VLAN offload support for AX88179A Birger Koblitz
2026-09-04 17:28 ` [PATCH net-next v10 10/15] ax88179_178a: Add AX179A/AX279 multicast configuration Birger Koblitz
2026-09-04 17:28 ` [PATCH net-next v10 11/15] ax88179_178a: Add Suspend/resume support for AX88179A/772D/279 Birger Koblitz
2026-09-04 17:28 ` [PATCH net-next v10 12/15] ax88179_178a: Add ethtool get_drvinfo Birger Koblitz
2026-09-04 17:28 ` [PATCH net-next v10 13/15] ax88179_178a: Update driver name and information Birger Koblitz
2026-09-04 17:28 ` [PATCH net-next v10 14/15] ax88179_178a: Add support for AX88179A/772D/279 EEPROM access Birger Koblitz
2026-09-04 17:28 ` [PATCH net-next v10 15/15] ax88796b: Add support for AX88772D, AX88179A and AX88279 Birger Koblitz
2026-09-06 10:40 ` [PATCH net-next v10 00/15] ax88179_178a: Add support for AX88179A-based chips Jianhui Xu
2026-09-06 18:56 ` Birger Koblitz
2026-09-07 5:04 ` Jianhui Xu
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=2eddb9fe-22b3-4fe4-a2ab-e408e4a726e7@birger-koblitz.de \
--to=mail@birger-koblitz.de \
--cc=andrew+netdev@lunn.ch \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=neuromoments@gmail.com \
--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 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.