From: "Krzysztof Hałasa" <khalasa@piap.pl>
To: Paolo Abeni <pabeni@redhat.com>
Cc: netdev <netdev@vger.kernel.org>,
Oliver Neukum <oneukum@suse.com>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>,
linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
Jose Ignacio Tornos Martinez <jtornosm@redhat.com>,
Ming Lei <ming.lei@redhat.com>,
Oleksij Rempel <o.rempel@pengutronix.de>
Subject: Re: [PATCH REPOST] usbnet: asix: leave the carrier control to phylink
Date: Wed, 09 Apr 2025 11:07:07 +0200 [thread overview]
Message-ID: <m3ecy1d7pg.fsf@t19.piap.pl> (raw)
In-Reply-To: <d5e03a72-bff3-4df1-91ed-6916abaaa0ec@redhat.com> (Paolo Abeni's message of "Tue, 8 Apr 2025 15:29:14 +0200")
Paolo Abeni <pabeni@redhat.com> writes:
> Does not build:
>
> ../drivers/net/usb/asix_devices.c:1396:19: error: ‘asix_status’
> undeclared here (not in a function); did you mean ‘si_status’?
> 1396 | .status = asix_status,
Right, thanks - somehow I didn't realize the recent addition in net-next
will break it. Should have been obvious.
Not a factor in v2, though.
--
Krzysztof "Chris" Hałasa
Sieć Badawcza Łukasiewicz
Przemysłowy Instytut Automatyki i Pomiarów PIAP
Al. Jerozolimskie 202, 02-486 Warszawa
prev parent reply other threads:[~2025-04-09 9:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-07 12:08 [PATCH REPOST] usbnet: asix: leave the carrier control to phylink Krzysztof Hałasa
2025-04-07 13:38 ` Oleksij Rempel
2025-04-08 11:55 ` Krzysztof Hałasa
2025-04-08 11:59 ` [PATCH v2] usbnet: asix AX88772: " Krzysztof Hałasa
2025-04-08 15:22 ` Jakub Kicinski
2025-04-10 12:14 ` Oleksij Rempel
2025-04-11 2:20 ` patchwork-bot+netdevbpf
2025-04-08 13:29 ` [PATCH REPOST] usbnet: asix: " Paolo Abeni
2025-04-09 9:07 ` Krzysztof Hałasa [this message]
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=m3ecy1d7pg.fsf@t19.piap.pl \
--to=khalasa@piap.pl \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=jtornosm@redhat.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=ming.lei@redhat.com \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=oneukum@suse.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 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).