Re: [PATCH 2/3] gpio: mockup: add locking

2018-11-20 Thread Linus Walleij
On Mon, Nov 19, 2018 at 10:09 AM Bartosz Golaszewski wrote: > pt., 16 lis 2018 o 22:43 Linus Walleij napisał(a): > > __gpio_* > > I tend to dislike __underscore_notation because I feel it > > is semantically ambguous. I prefer a proper name, even > > to the point that I prefer

Re: [PATCH 2/3] gpio: mockup: add locking

2018-11-20 Thread Linus Walleij
On Mon, Nov 19, 2018 at 10:09 AM Bartosz Golaszewski wrote: > pt., 16 lis 2018 o 22:43 Linus Walleij napisał(a): > > __gpio_* > > I tend to dislike __underscore_notation because I feel it > > is semantically ambguous. I prefer a proper name, even > > to the point that I prefer

Re: [PATCH 2/3] gpio: mockup: add locking

2018-11-19 Thread Bartosz Golaszewski
pt., 16 lis 2018 o 22:43 Linus Walleij napisał(a): > > On Thu, Nov 8, 2018 at 5:53 PM Bartosz Golaszewski wrote: > > > While no user reported any race condition problems with gpio-mockup, > > let's be on the safe side and use a mutex when performing any changes > > on the dummy chip structures.

Re: [PATCH 2/3] gpio: mockup: add locking

2018-11-19 Thread Bartosz Golaszewski
pt., 16 lis 2018 o 22:43 Linus Walleij napisał(a): > > On Thu, Nov 8, 2018 at 5:53 PM Bartosz Golaszewski wrote: > > > While no user reported any race condition problems with gpio-mockup, > > let's be on the safe side and use a mutex when performing any changes > > on the dummy chip structures.

Re: [PATCH 2/3] gpio: mockup: add locking

2018-11-16 Thread Linus Walleij
On Thu, Nov 8, 2018 at 5:53 PM Bartosz Golaszewski wrote: > While no user reported any race condition problems with gpio-mockup, > let's be on the safe side and use a mutex when performing any changes > on the dummy chip structures. > > Suggested-by: Uwe Kleine-König > Signed-off-by: Bartosz

Re: [PATCH 2/3] gpio: mockup: add locking

2018-11-16 Thread Linus Walleij
On Thu, Nov 8, 2018 at 5:53 PM Bartosz Golaszewski wrote: > While no user reported any race condition problems with gpio-mockup, > let's be on the safe side and use a mutex when performing any changes > on the dummy chip structures. > > Suggested-by: Uwe Kleine-König > Signed-off-by: Bartosz

Re: [PATCH 2/3] gpio: mockup: add locking

2018-11-08 Thread Uwe Kleine-König
On Thu, Nov 08, 2018 at 05:52:54PM +0100, Bartosz Golaszewski wrote: > While no user reported any race condition problems with gpio-mockup, > let's be on the safe side and use a mutex when performing any changes > on the dummy chip structures. > > Suggested-by: Uwe Kleine-König > Signed-off-by:

Re: [PATCH 2/3] gpio: mockup: add locking

2018-11-08 Thread Uwe Kleine-König
On Thu, Nov 08, 2018 at 05:52:54PM +0100, Bartosz Golaszewski wrote: > While no user reported any race condition problems with gpio-mockup, > let's be on the safe side and use a mutex when performing any changes > on the dummy chip structures. > > Suggested-by: Uwe Kleine-König > Signed-off-by:

[PATCH 2/3] gpio: mockup: add locking

2018-11-08 Thread Bartosz Golaszewski
While no user reported any race condition problems with gpio-mockup, let's be on the safe side and use a mutex when performing any changes on the dummy chip structures. Suggested-by: Uwe Kleine-König Signed-off-by: Bartosz Golaszewski --- drivers/gpio/gpio-mockup.c | 50

[PATCH 2/3] gpio: mockup: add locking

2018-11-08 Thread Bartosz Golaszewski
While no user reported any race condition problems with gpio-mockup, let's be on the safe side and use a mutex when performing any changes on the dummy chip structures. Suggested-by: Uwe Kleine-König Signed-off-by: Bartosz Golaszewski --- drivers/gpio/gpio-mockup.c | 50