From: "gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>
To: 胡连勤 <hulianqin@vivo.com>
Cc: "quic_prashk@quicinc.com" <quic_prashk@quicinc.com>,
"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>
Subject: Re: 答复: [PATCH] usb: gadget: u_serial: check Null pointer in EP callback
Date: Fri, 16 Aug 2024 13:57:03 +0200 [thread overview]
Message-ID: <2024081629-nebulizer-harvest-2303@gregkh> (raw)
In-Reply-To: <TYUPR06MB621717DE00C464BE67650C16D2812@TYUPR06MB6217.apcprd06.prod.outlook.com>
A: http://en.wikipedia.org/wiki/Top_post
Q: Were do I find info about this thing called top-posting?
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?
A: Top-posting.
Q: What is the most annoying thing in e-mail?
A: No.
Q: Should I include quotations after my reply?
http://daringfireball.net/2007/07/on_top
On Fri, Aug 16, 2024 at 11:16:08AM +0000, 胡连勤 wrote:
> Hello linux community expert:
>
> Q: What is causing driver_data to be NULL? And what protects it from happening right after you check for it?
> A: This is a very in-depth question, and I need to have a deeper understanding of the code before I can answer it.
> Judging from the crash stack, this patch currently has improved the crash problem.
Please figure this out, we can't take changes that don't actually fix
the root problem for obvious reasons (and you wouldn't want us to
either.)
thanks,
greg k-h
prev parent reply other threads:[~2024-08-16 11:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-16 10:49 [PATCH] usb: gadget: u_serial: check Null pointer in EP callback 胡连勤
2024-08-16 11:01 ` gregkh
2024-08-16 11:16 ` 答复: " 胡连勤
2024-08-16 11:57 ` gregkh [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=2024081629-nebulizer-harvest-2303@gregkh \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=hulianqin@vivo.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox