On Tue, Apr 5, 2016 at 5:58 AM, Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> 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?
> 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?
Linus
--
To unsubscribe from this list: send the line "unsubscribe stable" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html