From: Olivier Fourdan ofour...@redhat.com
WaitForDevice() can take an optional timeout parameter
but that timeout should be passed down to WaitForEventOfType()
and in turn to WaitForEvent()
Signed-off-by: Olivier Fourdan ofour...@redhat.com
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
On 07/26/2012 11:51 PM, Peter Hutterer wrote:
From: Olivier Fourdan ofour...@redhat.com
WaitForDevice() can take an optional timeout parameter
but that timeout should be passed down to WaitForEventOfType()
and in turn to WaitForEvent()
Signed-off-by: Olivier Fourdan ofour...@redhat.com
Hi!
No comments and no commits for my patches in the last week.
Is there a procedure I should follow so these don't get dropped, or
should I just be more patient because it's holiday season? :)
Should I keep sending patches in the meantime? (Lots more to come.)
Thanks,
Thomas
On 12-07-27 01:20 AM, Peter Hutterer wrote:
On Thu, Jul 26, 2012 at 10:11:55PM -0700, Alan Coopersmith wrote:
On 07/26/12 09:04 PM, Peter Hutterer wrote:
Running it before dist/distcheck/install is a bit pointless
Isn't the point there to clean up leftovers from previous builds and
ensure
On 12-07-27 12:05 AM, Peter Hutterer wrote:
Add a new command to stop each module after the given stage.
Main use-case:
build.sh --clone --stop-at clone
to quickly clone the source tree without building.
Signed-off-by: Peter Hutterer peter.hutte...@who-t.net
---
There's an argument to
On 12-07-27 04:19 PM, Gaetan Nadon wrote:
On 12-07-27 12:05 AM, Peter Hutterer wrote:
Add a new command to stop each module after the given stage.
Main use-case:
build.sh --clone --stop-at clone
to quickly clone the source tree without building.
Signed-off-by: Peter Hutterer
