From: Greg KH <gregkh@linuxfoundation.org>
To: ktestrobot@126.com, U201911841@hust.edu.cn
Cc: lidaxian@hust.edu.cn, hust-os-kernel-patches@googlegroups.com,
dzm91@hust.edu.cn, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, balbi@kernel.org,
s.shtylyov@omp.ru
Subject: Re: [PATCH v2] usb: phy: phy-tahvo: fix memory leak in tahvo_usb_probe()
Date: Tue, 25 Apr 2023 07:15:39 +0200 [thread overview]
Message-ID: <ZEdh-_Jv02qb6K4n@kroah.com> (raw)
In-Reply-To: <644741EB.013E97.00008@m126.mail.126.com>
On Tue, Apr 25, 2023 at 10:58:51AM +0800, ktestrobot@126.com wrote:
> Hi, Li Yang
> This email is automatically replied by KTestRobot(Beta). Please do not reply to this email.
But I will!
> If you have any questions or suggestions about KTestRobot, please contact ZhongYong <U201911841@hust.edu.cn>
First question, why are you responding from an email that is not allowed
to be responded to and forced to have us manually add an address?
That's not very nice or helpful for us who have to see these messages,
please fix that.
> --- Changed Paths ---
> drivers/usb/phy/phy-tahvo.c
> --- Log Message ---
> Smatch reports:
> drivers/usb/phy/phy-tahvo.c: tahvo_usb_probe()
> warn: missing unwind goto?
>
> After geting irq, if ret < 0, it will return without error handling to
> free memory.
> Just add error handling to fix this problem.
>
> --- Test Result ---
> *** CheckPatch PASS ***
> *** CheckSmatch PASS ***
> *** ApplyToLinuxNext PASS ***
Why is only "does the patch apply" matter for this bot? What is it
supposed to be doing here? Is it going to run on every single patch to
this mailing list, and if so, how can we turn it off as "it applied!" is
a very very low bar to be testing something for, and we already have a
bot that does this.
thanks,
greg k-h
next parent reply other threads:[~2023-04-25 5:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <644741EB.013E97.00008@m126.mail.126.com>
2023-04-25 5:15 ` Greg KH [this message]
2023-04-25 5:32 ` [PATCH v2] usb: phy: phy-tahvo: fix memory leak in tahvo_usb_probe() Dongliang Mu
2023-04-25 5:50 ` Greg KH
2023-04-25 5:57 ` Dongliang Mu
2023-04-20 14:08 Li Yang
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=ZEdh-_Jv02qb6K4n@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=U201911841@hust.edu.cn \
--cc=balbi@kernel.org \
--cc=dzm91@hust.edu.cn \
--cc=hust-os-kernel-patches@googlegroups.com \
--cc=ktestrobot@126.com \
--cc=lidaxian@hust.edu.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=s.shtylyov@omp.ru \
/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