Re: [RFC 6/7] iio: Refuse to register triggers with duplicate names

2016-06-11 Thread Jonathan Cameron
On 31/05/16 15:03, Lars-Peter Clausen wrote: > On 05/30/2016 02:49 PM, Crestez Dan Leonard wrote: >> On 05/29/2016 10:48 PM, Jonathan Cameron wrote: >>> On 23/05/16 19:40, Crestez Dan Leonard wrote: The trigger name is documented as unique but drivers are currently allowed to register

Re: [RFC 6/7] iio: Refuse to register triggers with duplicate names

2016-06-11 Thread Jonathan Cameron
On 31/05/16 15:03, Lars-Peter Clausen wrote: > On 05/30/2016 02:49 PM, Crestez Dan Leonard wrote: >> On 05/29/2016 10:48 PM, Jonathan Cameron wrote: >>> On 23/05/16 19:40, Crestez Dan Leonard wrote: The trigger name is documented as unique but drivers are currently allowed to register

Re: [RFC 6/7] iio: Refuse to register triggers with duplicate names

2016-05-31 Thread Lars-Peter Clausen
On 05/30/2016 02:49 PM, Crestez Dan Leonard wrote: > On 05/29/2016 10:48 PM, Jonathan Cameron wrote: >> On 23/05/16 19:40, Crestez Dan Leonard wrote: >>> The trigger name is documented as unique but drivers are currently >>> allowed to register triggers with duplicate names. This should be >>>

Re: [RFC 6/7] iio: Refuse to register triggers with duplicate names

2016-05-31 Thread Lars-Peter Clausen
On 05/30/2016 02:49 PM, Crestez Dan Leonard wrote: > On 05/29/2016 10:48 PM, Jonathan Cameron wrote: >> On 23/05/16 19:40, Crestez Dan Leonard wrote: >>> The trigger name is documented as unique but drivers are currently >>> allowed to register triggers with duplicate names. This should be >>>

Re: [RFC 6/7] iio: Refuse to register triggers with duplicate names

2016-05-30 Thread Crestez Dan Leonard
On 05/29/2016 10:48 PM, Jonathan Cameron wrote: > On 23/05/16 19:40, Crestez Dan Leonard wrote: >> The trigger name is documented as unique but drivers are currently >> allowed to register triggers with duplicate names. This should be >> considered a bug since it makes the 'current_trigger'

Re: [RFC 6/7] iio: Refuse to register triggers with duplicate names

2016-05-30 Thread Crestez Dan Leonard
On 05/29/2016 10:48 PM, Jonathan Cameron wrote: > On 23/05/16 19:40, Crestez Dan Leonard wrote: >> The trigger name is documented as unique but drivers are currently >> allowed to register triggers with duplicate names. This should be >> considered a bug since it makes the 'current_trigger'

Re: [RFC 6/7] iio: Refuse to register triggers with duplicate names

2016-05-29 Thread Jonathan Cameron
On 23/05/16 19:40, Crestez Dan Leonard wrote: > The trigger name is documented as unique but drivers are currently > allowed to register triggers with duplicate names. This should be > considered a bug since it makes the 'current_trigger' interface > unusable. > > Signed-off-by: Crestez Dan

Re: [RFC 6/7] iio: Refuse to register triggers with duplicate names

2016-05-29 Thread Jonathan Cameron
On 23/05/16 19:40, Crestez Dan Leonard wrote: > The trigger name is documented as unique but drivers are currently > allowed to register triggers with duplicate names. This should be > considered a bug since it makes the 'current_trigger' interface > unusable. > > Signed-off-by: Crestez Dan