On 17 Jan 2015, at 11:06, Jim Smith j...@insec.sh wrote:
On 2 Jan 2015, at 4:15 pm, David Gwynne da...@gwynne.id.au wrote:
can someone test this?
it allocates storage for the volume change details rather than cast
arguments to a single global task.
adds some safety while there if
On 2 Jan 2015, at 4:15 pm, David Gwynne da...@gwynne.id.au wrote:
can someone test this?
it allocates storage for the volume change details rather than cast
arguments to a single global task.
adds some safety while there if audio0 is a hotplug device.
ok?
The keyboard audio controls
On 3 Jan 2015, at 9:35 am, David Gwynne da...@gwynne.id.au wrote:
On 2 Jan 2015, at 9:55 pm, Mark Kettenis mark.kette...@xs4all.nl wrote:
Date: Fri, 2 Jan 2015 16:15:07 +1000
From: David Gwynne da...@gwynne.id.au
can someone test this?
it allocates storage for the volume change
Date: Fri, 2 Jan 2015 16:15:07 +1000
From: David Gwynne da...@gwynne.id.au
can someone test this?
it allocates storage for the volume change details rather than cast
arguments to a single global task.
adds some safety while there if audio0 is a hotplug device.
ok?
The problem with
On 2 Jan 2015, at 9:55 pm, Mark Kettenis mark.kette...@xs4all.nl wrote:
Date: Fri, 2 Jan 2015 16:15:07 +1000
From: David Gwynne da...@gwynne.id.au
can someone test this?
it allocates storage for the volume change details rather than cast
arguments to a single global task.
adds some
can someone test this?
it allocates storage for the volume change details rather than cast
arguments to a single global task.
adds some safety while there if audio0 is a hotplug device.
ok?
Index: audio.c
===
RCS file:
