From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: kernel test robot <lkp@intel.com>
Cc: linux-usb@vger.kernel.org
Subject: Re: [usb:usb-testing] BUILD SUCCESS WITH UNVERIFIED WARNING 25e531b422dc2ac90cdae3b6e74b5cdeb081440d
Date: Fri, 3 Apr 2026 08:37:14 +0200 [thread overview]
Message-ID: <2026040343-gnat-aqueduct-753c@gregkh> (raw)
In-Reply-To: <202604031342.WrjEctjz-lkp@intel.com>
On Fri, Apr 03, 2026 at 01:18:52PM +0800, kernel test robot wrote:
> tree/branch: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git usb-testing
> branch HEAD: 25e531b422dc2ac90cdae3b6e74b5cdeb081440d usb: xhci: Make usb_host_endpoint.hcpriv survive endpoint_disable()
>
> Unverified Warning (likely false positive, kindly check if interested):
>
> drivers/usb/typec/tcpm/fusb302.c:1790 fusb302_probe() warn: 'chip->gpio_int_n_irq' from request_threaded_irq() not released on lines: 1779.
Nice, this is an older issue, good catch! But not directly related to
the change that is currently in this tree at the moment.
thanks,
greg k-h
prev parent reply other threads:[~2026-04-03 6:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-03 5:18 [usb:usb-testing] BUILD SUCCESS WITH UNVERIFIED WARNING 25e531b422dc2ac90cdae3b6e74b5cdeb081440d kernel test robot
2026-04-03 6:37 ` Greg Kroah-Hartman [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=2026040343-gnat-aqueduct-753c@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=lkp@intel.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