On Tue, Mar 03, 2015 at 01:18:52PM -0800, Dmitry Torokhov wrote:
> On Sat, Feb 07, 2015 at 06:06:15PM +0800, Greg Kroah-Hartman wrote:
> > On Tue, Feb 03, 2015 at 03:12:19PM -0800, Dmitry Torokhov wrote:
> > > On Fri, Jan 16, 2015 at 03:33:09PM -0800, Dmitry Torokhov wrote:
> > > > This series is a
On Sat, Feb 07, 2015 at 06:06:15PM +0800, Greg Kroah-Hartman wrote:
> On Tue, Feb 03, 2015 at 03:12:19PM -0800, Dmitry Torokhov wrote:
> > On Fri, Jan 16, 2015 at 03:33:09PM -0800, Dmitry Torokhov wrote:
> > > This series is a combination of changes proposed by Luis a couple months
> > > ago and im
On Tue, Feb 03, 2015 at 03:12:19PM -0800, Dmitry Torokhov wrote:
> On Fri, Jan 16, 2015 at 03:33:09PM -0800, Dmitry Torokhov wrote:
> > This series is a combination of changes proposed by Luis a couple months
> > ago and implementation used by Chrome OS. The issue we are trying to solve
> > here is
On Fri, Jan 16, 2015 at 03:33:09PM -0800, Dmitry Torokhov wrote:
> This series is a combination of changes proposed by Luis a couple months
> ago and implementation used by Chrome OS. The issue we are trying to solve
> here is "slow" devices and drivers spending "too much time" in their probe()
> m
This series is a combination of changes proposed by Luis a couple months
ago and implementation used by Chrome OS. The issue we are trying to solve
here is "slow" devices and drivers spending "too much time" in their probe()
methods and it affects:
- overall kernel boot process when drivers are co
5 matches
Mail list logo