From: Jakub Kicinski <kuba@kernel.org>
To: Wei Jie Law <law.wei.jie@gt.tech.gov.sg>
Cc: Thangaraj Samynathan <Thangaraj.S@microchip.com>,
UNGLinuxDriver@microchip.com, Andrew Lunn <andrew+netdev@lunn.ch>,
"David S . Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@kernel.org>,
Paolo Abeni <pabeni@redhat.com>,
Woojung Huh <woojung.huh@microchip.com>,
netdev@vger.kernel.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, Wei Jie Law <98lawweijie@gmail.com>
Subject: Re: [PATCH net-next v5 0/2] net: usb: lan78xx: do not use uninitialized data after short reads
Date: Fri, 13 Nov 2026 16:32:19 -0800 [thread overview]
Message-ID: <20261113163219.16603c83@kernel.org> (raw)
In-Reply-To: <20261111013454.34542-1-law.wei.jie@gt.tech.gov.sg>
On Wed, 11 Nov 2026 09:34:52 +0800 Wei Jie Law wrote:
> Testing: the series builds without warnings (W=1) on net-next and passes
> checkpatch --strict. It applies unchanged to v6.12.105, where it was
> tested with a LAN7800 emulated by raw-gadget + dummy_hcd, booted with
> init_on_alloc=0:
Why are you testing this on 6.12 if you're just using a gadget and not
a real device?
next prev parent reply other threads:[~2026-11-14 0:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-11 1:34 [PATCH net-next v5 0/2] net: usb: lan78xx: do not use uninitialized data after short reads Wei Jie Law
2026-11-11 1:34 ` [PATCH net-next v5 1/2] net: usb: lan78xx: do not update statistics after a failed read Wei Jie Law
2026-11-11 1:34 ` [PATCH net-next v5 2/2] net: usb: lan78xx: reject short register and statistics transfers Wei Jie Law
2026-11-14 0:32 ` Jakub Kicinski [this message]
2026-11-14 0:40 ` [PATCH net-next v5 0/2] net: usb: lan78xx: do not use uninitialized data after short reads patchwork-bot+netdevbpf
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=20261113163219.16603c83@kernel.org \
--to=kuba@kernel.org \
--cc=98lawweijie@gmail.com \
--cc=Thangaraj.S@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@kernel.org \
--cc=law.wei.jie@gt.tech.gov.sg \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=woojung.huh@microchip.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.