On Fri, 2013-03-15 at 15:43 +0100, David Henningsson wrote:
> On 03/14/2013 04:17 PM, Tanu Kaskinen wrote:
> > On Thu, 2013-03-14 at 15:02 +0100, David Henningsson wrote:
> >> On 02/20/2013 07:24 PM, Tanu Kaskinen wrote:
> >>> The flag will be used in the upcoming pa_device_port_update_proplist()
>
On 03/14/2013 04:17 PM, Tanu Kaskinen wrote:
On Thu, 2013-03-14 at 15:02 +0100, David Henningsson wrote:
On 02/20/2013 07:24 PM, Tanu Kaskinen wrote:
The flag will be used in the upcoming pa_device_port_update_proplist()
function.
If the flag's function is to protect against an initial change
On Thu, 2013-03-14 at 17:17 +0200, Tanu Kaskinen wrote:
> On Thu, 2013-03-14 at 15:02 +0100, David Henningsson wrote:
> > On 02/20/2013 07:24 PM, Tanu Kaskinen wrote:
> > > The flag will be used in the upcoming pa_device_port_update_proplist()
> > > function.
> >
> > If the flag's function is to p
On Thu, 2013-03-14 at 15:02 +0100, David Henningsson wrote:
> On 02/20/2013 07:24 PM, Tanu Kaskinen wrote:
> > The flag will be used in the upcoming pa_device_port_update_proplist()
> > function.
>
> If the flag's function is to protect against an initial change
> notification, does it really wor
On 02/20/2013 07:24 PM, Tanu Kaskinen wrote:
The flag will be used in the upcoming pa_device_port_update_proplist()
function.
If the flag's function is to protect against an initial change
notification, does it really work? init_eld_ctls is called after
pa_card_new in module-alsa-card.c.
If
The flag will be used in the upcoming pa_device_port_update_proplist()
function.
---
src/pulsecore/card.c| 25 -
src/pulsecore/device-port.c | 12
src/pulsecore/device-port.h |6 ++
3 files changed, 38 insertions(+), 5 deletions(-)
diff --g
