From: "Andy Guo (郭卫斌)" <guoweibin@inspur.com>
To: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
Cc: "b-liu@ti.com" <b-liu@ti.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: RE: 答复: [vger.kernel.org代发]Re: [PATCH v2] usb: musb: Fix musb_gadget.c rxstate may cause request->buf overflow problems
Date: Thu, 28 Jul 2022 12:24:41 +0000 [thread overview]
Message-ID: <7ab29bb9ed094ee593ebcf2e351665dd@inspur.com> (raw)
In-Reply-To: <YuIzOeJZ7YKe4KDZ@kroah.com>
[-- Attachment #1: Type: text/plain, Size: 820 bytes --]
I'm sorroy,
I use Enterprise mailbox doesn't work very well.
I will send this patch through another mailbox.
Thanks
guoweibin
-----Original Message-----
From: gregkh@linuxfoundation.org <gregkh@linuxfoundation.org>
Sent: Thursday, July 28, 2022 2:57 PM
To: Andy Guo (郭卫斌) <guoweibin@inspur.com>
Cc: b-liu@ti.com; linux-usb@vger.kernel.org; linux-kernel@vger.kernel.org
Subject: Re: 答复: [vger.kernel.org代发]Re: [PATCH v2] usb: musb: Fix musb_gadget.c rxstate may cause request->buf overflow problems
On Thu, Jul 28, 2022 at 01:14:17AM +0000, Andy Guo (郭卫斌) wrote:
As can be seen in the archives:
https://lore.kernel.org/all/2c234d13d7274763b0102b83ce65b8ff@inspur.com/
this message could not be decoded, sorry.
Please resend in plain text format.
thanks,
greg k-h
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 2867 bytes --]
prev parent reply other threads:[~2022-07-28 12:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 8:43 [PATCH v2] usb: musb: Fix musb_gadget.c rxstate may cause request->buf overflow problems Andy Guo (郭卫斌)
2022-07-27 9:25 ` gregkh
2022-07-28 1:14 ` 答复: [vger.kernel.org代发]Re: " Andy Guo (郭卫斌)
2022-07-28 6:56 ` gregkh
2022-07-28 12:24 ` Andy Guo (郭卫斌) [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=7ab29bb9ed094ee593ebcf2e351665dd@inspur.com \
--to=guoweibin@inspur.com \
--cc=b-liu@ti.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).