On Wed, Jul 8, 2015 at 9:44 PM, Dmitry Torokhov
wrote:
> On Wed, Jul 08, 2015 at 06:00:41PM -0700, Dan Williams wrote:
>> On Wed, Jul 8, 2015 at 5:49 PM, Dmitry Torokhov
>> wrote:
>> > On Wed, Jul 08, 2015 at 05:36:04PM -0700, Dan Williams wrote:
>> >> On Mon, Jul 6, 2015 at 4:40 PM, Dmitry
On Wed, Jul 08, 2015 at 06:00:41PM -0700, Dan Williams wrote:
> On Wed, Jul 8, 2015 at 5:49 PM, Dmitry Torokhov
> wrote:
> > On Wed, Jul 08, 2015 at 05:36:04PM -0700, Dan Williams wrote:
> >> On Mon, Jul 6, 2015 at 4:40 PM, Dmitry Torokhov
> >> wrote:
> >> > On Tue, Jul 07, 2015 at 01:23:15AM
On Wed, Jul 8, 2015 at 5:49 PM, Dmitry Torokhov
wrote:
> On Wed, Jul 08, 2015 at 05:36:04PM -0700, Dan Williams wrote:
>> On Mon, Jul 6, 2015 at 4:40 PM, Dmitry Torokhov
>> wrote:
>> > On Tue, Jul 07, 2015 at 01:23:15AM +0200, Luis R. Rodriguez wrote:
>> >> On Sat, Jul 04, 2015 at 07:09:19AM
On Wed, Jul 08, 2015 at 05:54:26PM -0700, Dan Williams wrote:
> On Wed, Jul 8, 2015 at 5:52 PM, Dmitry Torokhov
> wrote:
> > On Wed, Jul 08, 2015 at 05:43:23PM -0700, Dan Williams wrote:
> >> On Mon, Jul 6, 2015 at 4:38 PM, Dmitry Torokhov
> >> wrote:
> >> > On Sat, Jul 04, 2015 at 07:09:19AM
On Wed, Jul 8, 2015 at 5:52 PM, Dmitry Torokhov
wrote:
> On Wed, Jul 08, 2015 at 05:43:23PM -0700, Dan Williams wrote:
>> On Mon, Jul 6, 2015 at 4:38 PM, Dmitry Torokhov
>> wrote:
>> > On Sat, Jul 04, 2015 at 07:09:19AM -0700, Dan Williams wrote:
>> >> The problem I ran into was needing to
On Wed, Jul 08, 2015 at 05:43:23PM -0700, Dan Williams wrote:
> On Mon, Jul 6, 2015 at 4:38 PM, Dmitry Torokhov
> wrote:
> > On Sat, Jul 04, 2015 at 07:09:19AM -0700, Dan Williams wrote:
> >> The problem I ran into was needing to remove devices that still had
> >> yet to be probed and not being
On Wed, Jul 08, 2015 at 05:36:04PM -0700, Dan Williams wrote:
> On Mon, Jul 6, 2015 at 4:40 PM, Dmitry Torokhov
> wrote:
> > On Tue, Jul 07, 2015 at 01:23:15AM +0200, Luis R. Rodriguez wrote:
> >> On Sat, Jul 04, 2015 at 07:09:19AM -0700, Dan Williams wrote:
> >> > On Fri, Jul 3, 2015 at 11:30
On Mon, Jul 6, 2015 at 4:38 PM, Dmitry Torokhov
wrote:
> On Sat, Jul 04, 2015 at 07:09:19AM -0700, Dan Williams wrote:
>> The problem I ran into was needing to remove devices that still had
>> yet to be probed and not being able to use registration completion vs
>> the device_lock() to
On Mon, Jul 6, 2015 at 4:40 PM, Dmitry Torokhov
wrote:
> On Tue, Jul 07, 2015 at 01:23:15AM +0200, Luis R. Rodriguez wrote:
>> On Sat, Jul 04, 2015 at 07:09:19AM -0700, Dan Williams wrote:
>> > On Fri, Jul 3, 2015 at 11:30 AM, Luis R. Rodriguez wrote:
>> > > On Sat, Jun 27, 2015 at 04:45:25PM
On Mon, Jul 6, 2015 at 4:38 PM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
On Sat, Jul 04, 2015 at 07:09:19AM -0700, Dan Williams wrote:
The problem I ran into was needing to remove devices that still had
yet to be probed and not being able to use registration completion vs
the
On Wed, Jul 08, 2015 at 05:43:23PM -0700, Dan Williams wrote:
On Mon, Jul 6, 2015 at 4:38 PM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
On Sat, Jul 04, 2015 at 07:09:19AM -0700, Dan Williams wrote:
The problem I ran into was needing to remove devices that still had
yet to be probed
On Wed, Jul 8, 2015 at 9:44 PM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
On Wed, Jul 08, 2015 at 06:00:41PM -0700, Dan Williams wrote:
On Wed, Jul 8, 2015 at 5:49 PM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
On Wed, Jul 08, 2015 at 05:36:04PM -0700, Dan Williams wrote:
On
On Wed, Jul 08, 2015 at 06:00:41PM -0700, Dan Williams wrote:
On Wed, Jul 8, 2015 at 5:49 PM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
On Wed, Jul 08, 2015 at 05:36:04PM -0700, Dan Williams wrote:
On Mon, Jul 6, 2015 at 4:40 PM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
On Mon, Jul 6, 2015 at 4:40 PM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
On Tue, Jul 07, 2015 at 01:23:15AM +0200, Luis R. Rodriguez wrote:
On Sat, Jul 04, 2015 at 07:09:19AM -0700, Dan Williams wrote:
On Fri, Jul 3, 2015 at 11:30 AM, Luis R. Rodriguez mcg...@suse.com wrote:
On Sat,
On Wed, Jul 8, 2015 at 5:49 PM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
On Wed, Jul 08, 2015 at 05:36:04PM -0700, Dan Williams wrote:
On Mon, Jul 6, 2015 at 4:40 PM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
On Tue, Jul 07, 2015 at 01:23:15AM +0200, Luis R. Rodriguez wrote:
On Wed, Jul 08, 2015 at 05:36:04PM -0700, Dan Williams wrote:
On Mon, Jul 6, 2015 at 4:40 PM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
On Tue, Jul 07, 2015 at 01:23:15AM +0200, Luis R. Rodriguez wrote:
On Sat, Jul 04, 2015 at 07:09:19AM -0700, Dan Williams wrote:
On Fri, Jul 3,
On Wed, Jul 08, 2015 at 05:54:26PM -0700, Dan Williams wrote:
On Wed, Jul 8, 2015 at 5:52 PM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
On Wed, Jul 08, 2015 at 05:43:23PM -0700, Dan Williams wrote:
On Mon, Jul 6, 2015 at 4:38 PM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
On Wed, Jul 8, 2015 at 5:52 PM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
On Wed, Jul 08, 2015 at 05:43:23PM -0700, Dan Williams wrote:
On Mon, Jul 6, 2015 at 4:38 PM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
On Sat, Jul 04, 2015 at 07:09:19AM -0700, Dan Williams wrote:
The
On Tue, Jul 7, 2015 at 1:23 AM, Luis R. Rodriguez wrote:
> On Sat, Jul 04, 2015 at 07:09:19AM -0700, Dan Williams wrote:
>> On Fri, Jul 3, 2015 at 11:30 AM, Luis R. Rodriguez wrote:
>> > On Sat, Jun 27, 2015 at 04:45:25PM -0700, Dan Williams wrote:
>> >> On Mon, Mar 30, 2015 at 4:20 PM, Dmitry
On Tue, Jul 7, 2015 at 1:23 AM, Luis R. Rodriguez mcg...@suse.com wrote:
On Sat, Jul 04, 2015 at 07:09:19AM -0700, Dan Williams wrote:
On Fri, Jul 3, 2015 at 11:30 AM, Luis R. Rodriguez mcg...@suse.com wrote:
On Sat, Jun 27, 2015 at 04:45:25PM -0700, Dan Williams wrote:
On Mon, Mar 30, 2015
On Mon, Jun 01, 2015 at 02:04:01PM +0200, Tomeu Vizoso wrote:
> On 29 May 2015 at 15:23, Tomeu Vizoso wrote:
> > On 29 May 2015 at 12:48, Tomeu Vizoso wrote:
> >> On 31 March 2015 at 01:20, Dmitry Torokhov
> >> wrote:
> >>> Some devices take a long time when initializing, and not all drivers
On Tue, Jul 07, 2015 at 01:23:15AM +0200, Luis R. Rodriguez wrote:
> On Sat, Jul 04, 2015 at 07:09:19AM -0700, Dan Williams wrote:
> > On Fri, Jul 3, 2015 at 11:30 AM, Luis R. Rodriguez wrote:
> > > On Sat, Jun 27, 2015 at 04:45:25PM -0700, Dan Williams wrote:
> > >> On Mon, Mar 30, 2015 at 4:20
On Sat, Jul 04, 2015 at 07:09:19AM -0700, Dan Williams wrote:
> On Fri, Jul 3, 2015 at 11:30 AM, Luis R. Rodriguez wrote:
> > On Sat, Jun 27, 2015 at 04:45:25PM -0700, Dan Williams wrote:
> >> On Mon, Mar 30, 2015 at 4:20 PM, Dmitry Torokhov
> >> wrote:
> >> > Some devices take a long time when
On Sat, Jun 27, 2015 at 04:45:25PM -0700, Dan Williams wrote:
> On Mon, Mar 30, 2015 at 4:20 PM, Dmitry Torokhov
> wrote:
> > Some devices take a long time when initializing, and not all drivers are
> > suited to initialize their devices when they are open. For example,
> > input drivers need to
On Sat, Jul 04, 2015 at 07:09:19AM -0700, Dan Williams wrote:
> On Fri, Jul 3, 2015 at 11:30 AM, Luis R. Rodriguez wrote:
> > On Sat, Jun 27, 2015 at 04:45:25PM -0700, Dan Williams wrote:
> >> On Mon, Mar 30, 2015 at 4:20 PM, Dmitry Torokhov
> >> wrote:
> >> > Some devices take a long time when
On Tue, Jul 07, 2015 at 01:23:15AM +0200, Luis R. Rodriguez wrote:
On Sat, Jul 04, 2015 at 07:09:19AM -0700, Dan Williams wrote:
On Fri, Jul 3, 2015 at 11:30 AM, Luis R. Rodriguez mcg...@suse.com wrote:
On Sat, Jun 27, 2015 at 04:45:25PM -0700, Dan Williams wrote:
On Mon, Mar 30, 2015 at
On Mon, Jun 01, 2015 at 02:04:01PM +0200, Tomeu Vizoso wrote:
On 29 May 2015 at 15:23, Tomeu Vizoso tomeu.viz...@gmail.com wrote:
On 29 May 2015 at 12:48, Tomeu Vizoso tomeu.viz...@gmail.com wrote:
On 31 March 2015 at 01:20, Dmitry Torokhov dmitry.torok...@gmail.com
wrote:
Some devices
On Sat, Jul 04, 2015 at 07:09:19AM -0700, Dan Williams wrote:
On Fri, Jul 3, 2015 at 11:30 AM, Luis R. Rodriguez mcg...@suse.com wrote:
On Sat, Jun 27, 2015 at 04:45:25PM -0700, Dan Williams wrote:
On Mon, Mar 30, 2015 at 4:20 PM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
Some
On Sat, Jun 27, 2015 at 04:45:25PM -0700, Dan Williams wrote:
On Mon, Mar 30, 2015 at 4:20 PM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
Some devices take a long time when initializing, and not all drivers are
suited to initialize their devices when they are open. For example,
input
On Sat, Jul 04, 2015 at 07:09:19AM -0700, Dan Williams wrote:
On Fri, Jul 3, 2015 at 11:30 AM, Luis R. Rodriguez mcg...@suse.com wrote:
On Sat, Jun 27, 2015 at 04:45:25PM -0700, Dan Williams wrote:
On Mon, Mar 30, 2015 at 4:20 PM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
Some
On Fri, Jul 3, 2015 at 11:30 AM, Luis R. Rodriguez wrote:
> On Sat, Jun 27, 2015 at 04:45:25PM -0700, Dan Williams wrote:
>> On Mon, Mar 30, 2015 at 4:20 PM, Dmitry Torokhov
>> wrote:
>> > Some devices take a long time when initializing, and not all drivers are
>> > suited to initialize their
On Fri, Jul 3, 2015 at 11:30 AM, Luis R. Rodriguez mcg...@suse.com wrote:
On Sat, Jun 27, 2015 at 04:45:25PM -0700, Dan Williams wrote:
On Mon, Mar 30, 2015 at 4:20 PM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
Some devices take a long time when initializing, and not all drivers are
On Sat, Jun 27, 2015 at 04:45:25PM -0700, Dan Williams wrote:
> On Mon, Mar 30, 2015 at 4:20 PM, Dmitry Torokhov
> wrote:
> > Some devices take a long time when initializing, and not all drivers are
> > suited to initialize their devices when they are open. For example,
> > input drivers need to
On Sat, Jun 27, 2015 at 04:45:25PM -0700, Dan Williams wrote:
On Mon, Mar 30, 2015 at 4:20 PM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
Some devices take a long time when initializing, and not all drivers are
suited to initialize their devices when they are open. For example,
input
On Mon, Mar 30, 2015 at 4:20 PM, Dmitry Torokhov
wrote:
> Some devices take a long time when initializing, and not all drivers are
> suited to initialize their devices when they are open. For example,
> input drivers need to interrogate their devices in order to publish
> device's capabilities
On Mon, Mar 30, 2015 at 4:20 PM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
Some devices take a long time when initializing, and not all drivers are
suited to initialize their devices when they are open. For example,
input drivers need to interrogate their devices in order to publish
On 29 May 2015 at 15:23, Tomeu Vizoso wrote:
> On 29 May 2015 at 12:48, Tomeu Vizoso wrote:
>> On 31 March 2015 at 01:20, Dmitry Torokhov wrote:
>>> Some devices take a long time when initializing, and not all drivers are
>>> suited to initialize their devices when they are open. For example,
On 29 May 2015 at 15:23, Tomeu Vizoso tomeu.viz...@gmail.com wrote:
On 29 May 2015 at 12:48, Tomeu Vizoso tomeu.viz...@gmail.com wrote:
On 31 March 2015 at 01:20, Dmitry Torokhov dmitry.torok...@gmail.com wrote:
Some devices take a long time when initializing, and not all drivers are
suited to
On 29 May 2015 at 12:48, Tomeu Vizoso wrote:
> On 31 March 2015 at 01:20, Dmitry Torokhov wrote:
>> Some devices take a long time when initializing, and not all drivers are
>> suited to initialize their devices when they are open. For example,
>> input drivers need to interrogate their devices
On 31 March 2015 at 01:20, Dmitry Torokhov wrote:
> Some devices take a long time when initializing, and not all drivers are
> suited to initialize their devices when they are open. For example,
> input drivers need to interrogate their devices in order to publish
> device's capabilities before
On 31 March 2015 at 01:20, Dmitry Torokhov dmitry.torok...@gmail.com wrote:
Some devices take a long time when initializing, and not all drivers are
suited to initialize their devices when they are open. For example,
input drivers need to interrogate their devices in order to publish
device's
On 29 May 2015 at 12:48, Tomeu Vizoso tomeu.viz...@gmail.com wrote:
On 31 March 2015 at 01:20, Dmitry Torokhov dmitry.torok...@gmail.com wrote:
Some devices take a long time when initializing, and not all drivers are
suited to initialize their devices when they are open. For example,
input
Some devices take a long time when initializing, and not all drivers are
suited to initialize their devices when they are open. For example,
input drivers need to interrogate their devices in order to publish
device's capabilities before userspace will open them. When such drivers
are compiled
Some devices take a long time when initializing, and not all drivers are
suited to initialize their devices when they are open. For example,
input drivers need to interrogate their devices in order to publish
device's capabilities before userspace will open them. When such drivers
are compiled
Some devices take a long time when initializing, and not all drivers are
suited to initialize their devices when they are open. For example,
input drivers need to interrogate their devices in order to publish
device's capabilities before userspace will open them. When such drivers
are compiled
Some devices take a long time when initializing, and not all drivers are
suited to initialize their devices when they are open. For example,
input drivers need to interrogate their devices in order to publish
device's capabilities before userspace will open them. When such drivers
are compiled
46 matches
Mail list logo
