From: patchwork-bot+netdevbpf@kernel.org
To: Diego Fernando Mancera Gomez <diegomancera.dev@gmail.com>
Cc: castet.matthieu@free.fr, stf_xl@wp.pl, 3chas3@gmail.com,
gregkh@linuxfoundation.org, mfo@igalia.com,
linux-usb@vger.kernel.org, netdev@vger.kernel.org,
linux-atm-general@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
syzbot+e62a973f8322b3bbe3ac@syzkaller.appspotmail.com
Subject: Re: [PATCH] usb: atm: ueagle-atm: reject descriptors that confuse probe and disconnect
Date: Thu, 23 Jul 2026 15:30:16 +0000 [thread overview]
Message-ID: <178482061640.2321119.12288067082123578966.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20260717080704.1264-1-diegomancera.dev@gmail.com>
Hello:
This patch was applied to netdev/net.git (main)
by Jakub Kicinski <kuba@kernel.org>:
On Fri, 17 Jul 2026 02:07:04 -0600 you wrote:
> uea_probe() distinguishes a pre-firmware device from a post-firmware one
> using the USB id (UEA_IS_PREFIRM()), and stores a different object as the
> interface data in each case: a 'struct completion' for a pre-firmware
> device (to be waited on in .disconnect()), or a 'struct usbatm_data' for a
> post-firmware one.
>
> uea_disconnect() instead tells the two apart by the number of interfaces
> of the active configuration (a pre-firmware device exposes a single
> interface, ADI930 has 2 and eagle has 3), and casts the interface data
> accordingly.
>
> [...]
Here is the summary with links:
- usb: atm: ueagle-atm: reject descriptors that confuse probe and disconnect
https://git.kernel.org/netdev/net/c/9dfd800b374c
You are awesome, thank you!
--
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html
prev parent reply other threads:[~2026-07-23 15:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-17 8:07 [PATCH] usb: atm: ueagle-atm: reject descriptors that confuse probe and disconnect Diego Fernando Mancera Gomez
2026-07-17 9:10 ` Stanislaw Gruszka
2026-07-23 15:30 ` patchwork-bot+netdevbpf [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=178482061640.2321119.12288067082123578966.git-patchwork-notify@kernel.org \
--to=patchwork-bot+netdevbpf@kernel.org \
--cc=3chas3@gmail.com \
--cc=castet.matthieu@free.fr \
--cc=diegomancera.dev@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-atm-general@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mfo@igalia.com \
--cc=netdev@vger.kernel.org \
--cc=stf_xl@wp.pl \
--cc=syzbot+e62a973f8322b3bbe3ac@syzkaller.appspotmail.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