[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <0C18FE92A7765D4EB9EE5D38D86A563A05D2B765@SHSMSX103.ccr.corp.intel.com>
Date: Wed, 4 May 2016 02:21:11 +0000
From: "Du, Changbin" <changbin.du@...el.com>
To: Greg KH <gregkh@...uxfoundation.org>,
Tony Battersby <tonyb@...ernetics.com>
CC: "stern@...land.harvard.edu" <stern@...land.harvard.edu>,
"baolu.lu@...ux.intel.com" <baolu.lu@...ux.intel.com>,
"chasemetzger15@...il.com" <chasemetzger15@...il.com>,
"balbi@...com" <balbi@...com>,
"kborer@...il.com" <kborer@...il.com>,
"mjg59@...eos.com" <mjg59@...eos.com>,
"jun.li@...escale.com" <jun.li@...escale.com>,
"Robert.Schlabbach@....net" <Robert.Schlabbach@....net>,
"linux-usb@...r.kernel.org" <linux-usb@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"joe.lawrence@...atus.com" <joe.lawrence@...atus.com>
Subject: RE: [PATCH] usb: hub: fix panic caused by NULL bos pointer during
reset device
> > I think Greg is referring to commit 464ad8c43a9e ("usb: core : hub: Fix
> > BOS 'NULL pointer' kernel panic"), which has already been applied
> > upstream. It looks to me like that patch might have fixed the same
> > problem in a different way, in which case Changbin's patch is not
> > needed. But I haven't been involved in developing or testing that
> > patch, so I can't say for sure. At the very least, 464ad8c43a9e
> > conflicts with Changbin's patch.
> >
> > Changbin, can you take a look at 464ad8c43a9e and see if that fixes the
> > same problem that your patch did?
>
> Given the lack of response here, I've dropped this from my queue. If
> it's still needed, someone must resend it.
>
> thanks,
>
> greg k-h
Hi,
I missed this email because it was junked by my email client. Just checked
patch 464ad8c43a9e, it fix the same issue. So my patch no longer need now.
Thanks for the patch.
Best Regards,
Du, Changbin
Powered by blists - more mailing lists