From: Greg KH <gregkh@linuxfoundation.org>
To: Dongliang Mu <dzm91@hust.edu.cn>
Cc: ktestrobot@126.com, U201911841@hust.edu.cn, lidaxian@hust.edu.cn,
hust-os-kernel-patches@googlegroups.com,
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:50:27 +0200 [thread overview]
Message-ID: <ZEdqIz8Vfd09zBFL@kroah.com> (raw)
In-Reply-To: <9c09cb12-05d1-7c50-0d99-945fd384e3a3@hust.edu.cn>
On Tue, Apr 25, 2023 at 01:32:35PM +0800, Dongliang Mu wrote:
>
> On 2023/4/25 13:15, Greg KH wrote:
> > 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.
>
> Hi greg,
>
> thanks for your feedback.
>
> This robot is only used for our internal patch review. It should not send
> any email out to Linux kernel mailing list.
But it did :(
> Sorry about this false alarm.
It happened more than once here, so please be more careful with the bot.
thanks,
greg k-h
next prev parent reply other threads:[~2023-04-25 5:50 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 ` [PATCH v2] usb: phy: phy-tahvo: fix memory leak in tahvo_usb_probe() Greg KH
2023-04-25 5:32 ` Dongliang Mu
2023-04-25 5:50 ` Greg KH [this message]
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=ZEdqIz8Vfd09zBFL@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 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.