From: Felipe Balbi <balbi@kernel.org>
To: "He\, Bo" <bo.he@intel.com>,
"linux-kernel\@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-usb\@vger.kernel.org" <linux-usb@vger.kernel.org>
Cc: "gregkh\@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"peter.chen\@nxp.com" <peter.chen@nxp.com>,
"k.opasiak\@samsung.com" <k.opasiak@samsung.com>,
"stefan\@agner.ch" <stefan@agner.ch>,
"felixhaedicke\@web.de" <felixhaedicke@web.de>,
"colin.king\@canonical.com" <colin.king@canonical.com>,
"rogerq\@ti.com" <rogerq@ti.com>,
"f.fainelli\@gmail.com" <f.fainelli@gmail.com>, "Zhang\,
Yanmin" <yanmin.zhang@intel.com>
Subject: RE: [PATCH] usb: gadget: udc: fix the kernel NULL pointer in composite_setup
Date: Wed, 19 Jul 2017 12:50:29 +0300 [thread overview]
Message-ID: <87bmog69i2.fsf@linux.intel.com> (raw)
In-Reply-To: <CD6925E8781EFD4D8E11882D20FC406D5280D382@SHSMSX104.ccr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 427 bytes --]
(No top-posting!)
"He, Bo" <bo.he@intel.com> writes:
> The patch I submitted is based on the latest kernel,
> I checked the latest kernel has the same logic,
> so I send the patch to LKML.
but you haven't reproduced the bug on latest kernel, have you?
Can you send me tracepoint output of one test run (without failures is
fine) I just wanna know what exactly it is that you're doing.
cheers
--
balbi
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2017-07-19 9:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-18 9:19 [PATCH] usb: gadget: udc: fix the kernel NULL pointer in composite_setup He, Bo
2017-07-18 10:44 ` Felipe Balbi
2017-07-19 5:16 ` He, Bo
2017-07-19 7:50 ` Felipe Balbi
2017-07-19 8:13 ` He, Bo
2017-07-19 9:50 ` Felipe Balbi [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=87bmog69i2.fsf@linux.intel.com \
--to=balbi@kernel.org \
--cc=bo.he@intel.com \
--cc=colin.king@canonical.com \
--cc=f.fainelli@gmail.com \
--cc=felixhaedicke@web.de \
--cc=gregkh@linuxfoundation.org \
--cc=k.opasiak@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@nxp.com \
--cc=rogerq@ti.com \
--cc=stefan@agner.ch \
--cc=yanmin.zhang@intel.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.