From: Krzysztof Kozlowski <krzk@kernel.org>
To: 胡连勤 <hulianqin@vivo.com>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"Michael Nazzareno Trimarchi" <michael@amarulasolutions.com>,
"Prashanth K" <quic_prashk@quicinc.com>
Cc: "quic_jjohnson@quicinc.com" <quic_jjohnson@quicinc.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"opensource.kernel" <opensource.kernel@vivo.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
Yuesong Li <liyuesong@vivo.com>
Subject: Re: 答复: [PATCH v9] usb: gadget: u_serial: Add null pointer check in gs_read_complete & gs_write_complete
Date: Mon, 2 Sep 2024 18:08:34 +0200 [thread overview]
Message-ID: <1179f9e8-1e5e-4658-8102-ee4d2c49575f@kernel.org> (raw)
In-Reply-To: <PUZPR06MB6224FF88145DAA364464EA7FD2922@PUZPR06MB6224.apcprd06.prod.outlook.com>
On 02/09/2024 16:38, 胡连勤 wrote:
> Ping......
>
You ping after four days? As whom do you treat us? I already complained
about @vivo.com in several threads. That's one more to the list of very
poor interactions from @vivo.com.
READ submitting-patches very carefully and then get your process fixed.
Best regards,
Krzysztof
next prev parent reply other threads:[~2024-09-02 16:08 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 11:54 [PATCH v9] usb: gadget: u_serial: Add null pointer check in gs_read_complete & gs_write_complete 胡连勤
2024-09-02 14:38 ` 答复: " 胡连勤
2024-09-02 16:08 ` Krzysztof Kozlowski [this message]
2024-09-03 2:23 ` 答复: " 胡连勤
2024-09-03 4:58 ` gregkh
2024-09-03 11:49 ` 答复: " 胡连勤
2024-09-03 12:05 ` gregkh
2024-09-02 16:16 ` Krzysztof Kozlowski
2024-09-03 6:26 ` gregkh
2024-09-03 11:58 ` 答复: " 胡连勤
2024-09-03 12:06 ` gregkh
-- strict thread matches above, loose matches on Subject: below --
2024-09-05 8:05 胡连勤
2024-09-25 6:29 胡连勤
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=1179f9e8-1e5e-4658-8102-ee4d2c49575f@kernel.org \
--to=krzk@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=hulianqin@vivo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=liyuesong@vivo.com \
--cc=michael@amarulasolutions.com \
--cc=opensource.kernel@vivo.com \
--cc=quic_jjohnson@quicinc.com \
--cc=quic_prashk@quicinc.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 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.