All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Sudip Mukherjee <sudipm.mukherjee@gmail.com>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	stable <stable@vger.kernel.org>,
	Ross Zwisler <ross.zwisler@linux.intel.com>
Subject: Re: [PATCH v2] parport: register driver later
Date: Tue, 5 Apr 2016 09:47:48 -0400	[thread overview]
Message-ID: <20160405134748.GA31683@kroah.com> (raw)
In-Reply-To: <CA+55aFxaXhSp9+Fa09rKHVge5-epMsEZsyyChmbRjPS=ohb-Sg@mail.gmail.com>

On Tue, Apr 05, 2016 at 06:44:12AM -0700, Linus Torvalds wrote:
> On Tue, Apr 5, 2016 at 5:58 AM, Greg KH <gregkh@linuxfoundation.org> 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

  reply	other threads:[~2016-04-05 13:47 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-06 15:10 [PATCH v2] parport: register driver later Sudip Mukherjee
2016-03-07 17:32 ` Ross Zwisler
2016-04-05  5:26   ` Sudip Mukherjee
2016-04-05 12:58     ` Greg KH
2016-04-05 13:17       ` Sudip Mukherjee
2016-04-05 13:42         ` Greg KH
2016-04-05 13:44       ` Linus Torvalds
2016-04-05 13:47         ` Greg KH [this message]
2016-04-05 14:07           ` Linus Torvalds
     [not found] ` <CA+55aFz0A07bbfSiCuBo4PPnEje1--zPSLuNzYrxqhj0gZFaWA@mail.gmail.com>
2016-04-05 11:54   ` Sudip Mukherjee

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=20160405134748.GA31683@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ross.zwisler@linux.intel.com \
    --cc=stable@vger.kernel.org \
    --cc=sudipm.mukherjee@gmail.com \
    --cc=torvalds@linux-foundation.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 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.