From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.linuxfoundation.org ([140.211.169.12]:49220 "EHLO mail.linuxfoundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932571AbcDENrt (ORCPT ); Tue, 5 Apr 2016 09:47:49 -0400 Date: Tue, 5 Apr 2016 09:47:48 -0400 From: Greg KH To: Linus Torvalds Cc: Sudip Mukherjee , Linux Kernel Mailing List , stable , Ross Zwisler Subject: Re: [PATCH v2] parport: register driver later Message-ID: <20160405134748.GA31683@kroah.com> References: <1457277010-30593-1-git-send-email-sudipm.mukherjee@gmail.com> <20160307173255.GA26456@linux.intel.com> <20160405052608.GA2625@sudip-tp> <20160405125830.GA25758@kroah.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Sender: stable-owner@vger.kernel.org List-ID: On Tue, Apr 05, 2016 at 06:44:12AM -0700, Linus Torvalds wrote: > On Tue, Apr 5, 2016 at 5:58 AM, Greg KH wrote: > > > > A bit better commit message here would have caused me to notice it. > > Something like "Revert a broken patch because it crashes all of our > > machines without it!!!" would be a hint it needed to go in :) > > Didn't my revert of e7223f1860 fix this? Yes. > > I think the lack of parport hardware around seems to have caused a total > > lack of testing this code path while it was in linux-next and in my > > local testing, sorry about that, it should have been caught a lot > > earlier. > > Well, the original 0day kernel test robot report was from the > linux-next days, back in February. I reverted the commit that the > kernel test robot indicated was the point where the actual trouble > started two weeks ago (commit 1701f680407c). > > I was hoping that would be it. Have there been reports since that I > haven't seen? Not that I have seen. But I missed the 0day report so I might not be the best judge here... thanks, greg k-h