From: "Woo-kwang Lee" <wookwang.lee@samsung.com>
To: "'Greg KH'" <gregkh@linuxfoundation.org>
Cc: <linux-usb@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<stable@vger.kernel.org>, <sj1557.seo@samsung.com>
Subject: RE: [PATCH] usb: core: add bos NULL pointer checking condition
Date: Wed, 4 Oct 2023 16:34:37 +0900 [thread overview]
Message-ID: <007e01d9f695$3a8d9ea0$afa8dbe0$@samsung.com> (raw)
In-Reply-To: <2023100411-duckling-tibia-398a@gregkh>
Hello. Grek.
It means that this is not needed.
Commit id f74a7afc224a already has hub_is_superspeedplus modification.
I'm sorry for the confusion.
Thank you.
Woo-kwang Lee
> -----Original Message-----
> From: 'Greg KH' <gregkh@linuxfoundation.org>
> Sent: Wednesday, October 4, 2023 4:22 PM
> To: Woo-kwang Lee <wookwang.lee@samsung.com>
> Cc: linux-usb@vger.kernel.org; linux-kernel@vger.kernel.org;
> stable@vger.kernel.org; sj1557.seo@samsung.com
> Subject: Re: [PATCH] usb: core: add bos NULL pointer checking condition
>
> On Wed, Oct 04, 2023 at 04:06:17PM +0900, Woo-kwang Lee wrote:
> > Hello. I think I missed the patch.
>
> I do not understand, does that mean that you have tested the patch (and
> which one, please do not top post), and that this is not needed?
>
> confused,
> greg k-h
prev parent reply other threads:[~2023-10-04 7:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20231004062700epcas1p16fe36bf6b6a6e5d9d4adeaef32937480@epcas1p1.samsung.com>
2023-10-04 6:26 ` [PATCH] usb: core: add bos NULL pointer checking condition Woo-kwang Lee
2023-10-04 6:36 ` Greg KH
2023-10-04 7:06 ` Woo-kwang Lee
2023-10-04 7:21 ` 'Greg KH'
2023-10-04 7:34 ` Woo-kwang Lee [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='007e01d9f695$3a8d9ea0$afa8dbe0$@samsung.com' \
--to=wookwang.lee@samsung.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sj1557.seo@samsung.com \
--cc=stable@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).