From: Ping-Ke Shih <pkshih@realtek.com>
To: Ping-Ke Shih <pkshih@realtek.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
stable <stable@kernel.org>
Subject: RE: [PATCH net] wifi: rtw88: properly drop usb interface reference on error
Date: Mon, 9 Mar 2026 00:43:24 +0000 [thread overview]
Message-ID: <24edddc6e31e4e369ceae3cd75e4378e@realtek.com> (raw)
In-Reply-To: <8f573000-97db-4b6c-83ff-a759ac3175cd@RTKEXHMBS05.realtek.com.tw>
Ping-Ke Shih <pkshih@realtek.com> wrote:
>
> Greg Kroah-Hartman <gregkh@linuxfoundation.org> wrote:
>
> > If an error happens in the usb probe path, in rtw_usb_intf_init(), the
> > usb interface reference needs to be properly dropped, otherwise is is
> > incorrectly increased when returning to the USB core.
> >
> > Cc: Ping-Ke Shih <pkshih@realtek.com>
> > Cc: stable <stable@kernel.org>
> > Assisted-by: gkh_clanker_2000
> > Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > Acked-by: Ping-Ke Shih <pkshih@realtek.com>
>
> 1 patch(es) applied to rtw-next branch of rtw.git, thanks.
>
> c413737effd6 wifi: rtw88: properly drop usb interface reference on error
>
As Johan shared patchset and discussion in [1], drop this patch.
[1] https://lore.kernel.org/linux-wireless/2026030625-wrongness-preorder-4e1e@gregkh/
prev parent reply other threads:[~2026-03-09 0:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-23 11:37 [PATCH net] wifi: rtw88: properly drop usb interface reference on error Greg Kroah-Hartman
2026-02-24 0:46 ` Ping-Ke Shih
2026-02-24 1:09 ` Greg Kroah-Hartman
2026-02-24 1:49 ` Ping-Ke Shih
2026-02-24 6:18 ` Greg Kroah-Hartman
2026-03-03 3:07 ` Ping-Ke Shih
2026-03-09 0:43 ` Ping-Ke Shih [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=24edddc6e31e4e369ceae3cd75e4378e@realtek.com \
--to=pkshih@realtek.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=stable@kernel.org \
/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.