Re: [PATCH v2 1/7] driver core: emit uevents when device is bound to a driver

2017-09-30 Thread Greg Kroah-Hartman
.@vger.kernel.org>; Guenter Roeck <li...@roeck-us.net>; Ruhl, > > > Michael J <michael.j.r...@intel.com> > > > Subject: Re: [PATCH v2 1/7] driver core: emit uevents when device is bound > > > to a driver > > > > > > On Wed, Jul 19, 2

Re: [PATCH v2 1/7] driver core: emit uevents when device is bound to a driver

2017-09-30 Thread Greg Kroah-Hartman
> > > Sent: Friday, September 29, 2017 3:37 PM > > > To: Dmitry Torokhov > > > Cc: Greg Kroah-Hartman ; Tejun Heo > > > ; Linux Kernel Mailing List > > ker...@vger.kernel.org>; Guenter Roeck ; Ruhl, > > > Michael J > > >

Re: [PATCH v2 1/7] driver core: emit uevents when device is bound to a driver

2017-09-29 Thread Dmitry Torokhov
dmitry.torok...@gmail.com> > > Cc: Greg Kroah-Hartman <gre...@linuxfoundation.org>; Tejun Heo > > <hte...@gmail.com>; Linux Kernel Mailing List > ker...@vger.kernel.org>; Guenter Roeck <li...@roeck-us.net>; Ruhl, > > Michael J <michael.j.r...@intel.co

Re: [PATCH v2 1/7] driver core: emit uevents when device is bound to a driver

2017-09-29 Thread Dmitry Torokhov
ov > > Cc: Greg Kroah-Hartman ; Tejun Heo > > ; Linux Kernel Mailing List > ker...@vger.kernel.org>; Guenter Roeck ; Ruhl, > > Michael J > > Subject: Re: [PATCH v2 1/7] driver core: emit uevents when device is bound > > to a driver > > > > On Wed, Jul

RE: [PATCH v2 1/7] driver core: emit uevents when device is bound to a driver

2017-09-29 Thread Ruhl, Michael J
tion.org>; Tejun Heo > <hte...@gmail.com>; Linux Kernel Mailing List ker...@vger.kernel.org>; Guenter Roeck <li...@roeck-us.net>; Ruhl, > Michael J <michael.j.r...@intel.com> > Subject: Re: [PATCH v2 1/7] driver core: emit uevents when device is bound > to a driver >

RE: [PATCH v2 1/7] driver core: emit uevents when device is bound to a driver

2017-09-29 Thread Ruhl, Michael J
l.org>; Guenter Roeck ; Ruhl, > Michael J > Subject: Re: [PATCH v2 1/7] driver core: emit uevents when device is bound > to a driver > > On Wed, Jul 19, 2017 at 5:24 PM, Dmitry Torokhov > wrote: > > There are certain touch controllers that may come up in either

Re: [PATCH v2 1/7] driver core: emit uevents when device is bound to a driver

2017-09-29 Thread Dan Williams
On Wed, Jul 19, 2017 at 5:24 PM, Dmitry Torokhov wrote: > There are certain touch controllers that may come up in either normal > (application) or boot mode, depending on whether firmware/configuration is > corrupted when they are powered on. In boot mode the kernel

Re: [PATCH v2 1/7] driver core: emit uevents when device is bound to a driver

2017-09-29 Thread Dan Williams
On Wed, Jul 19, 2017 at 5:24 PM, Dmitry Torokhov wrote: > There are certain touch controllers that may come up in either normal > (application) or boot mode, depending on whether firmware/configuration is > corrupted when they are powered on. In boot mode the kernel does not create > input device

[PATCH v2 1/7] driver core: emit uevents when device is bound to a driver

2017-07-19 Thread Dmitry Torokhov
There are certain touch controllers that may come up in either normal (application) or boot mode, depending on whether firmware/configuration is corrupted when they are powered on. In boot mode the kernel does not create input device instance (because it does not necessarily know the

[PATCH v2 1/7] driver core: emit uevents when device is bound to a driver

2017-07-19 Thread Dmitry Torokhov
There are certain touch controllers that may come up in either normal (application) or boot mode, depending on whether firmware/configuration is corrupted when they are powered on. In boot mode the kernel does not create input device instance (because it does not necessarily know the