On Tue, Apr 5, 2016 at 6:47 AM, Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
>>
>> I was hoping that would be it. Have there been reports since that I
>> haven't seen?
>
> Not that I have seen.
Ok. So as far as I can see we can ignore this for now (at at least be
no worse off than we used to be).
I didn't check *why* ppdev_init happens before the parport driver has
been initialized,
I get the feeling that the trivial fix would be to just make a new
"parport_init/exit()" pair that just does the parport_bus_init(). And
mark that as "subsys_initcall()" so that it gets done before the
individual drivers. No need to even be fancy about deferred probing
etc, just a simple "ppdev depends on parport" chain.
But I didn't look into the actual sequence of events, so it's entirely
possible I'm missing something.
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