On Wed, Nov 05, 2014 at 12:51:22PM +0100, Mariusz Gorski wrote:
On Wed, Nov 05, 2014 at 01:19:10PM +0300, Dan Carpenter wrote:
On Tue, Nov 04, 2014 at 10:47:19PM +0100, Mariusz Gorski wrote:
Fix the implementation of a single-open policy for both
devices (lcd and keypad) by using atomic_t
On Tue, Nov 04, 2014 at 10:47:19PM +0100, Mariusz Gorski wrote:
Fix the implementation of a single-open policy for both
devices (lcd and keypad) by using atomic_t instead of plain ints.
This seems like it might be a real life bug that you have experienced?
The changelog should tell the user
On Wed, Nov 05, 2014 at 01:19:10PM +0300, Dan Carpenter wrote:
On Tue, Nov 04, 2014 at 10:47:19PM +0100, Mariusz Gorski wrote:
Fix the implementation of a single-open policy for both
devices (lcd and keypad) by using atomic_t instead of plain ints.
This seems like it might be a real
Fix the implementation of a single-open policy for both
devices (lcd and keypad) by using atomic_t instead of plain ints.
Signed-off-by: Mariusz Gorski marius.gor...@gmail.com
---
drivers/staging/panel/panel.c | 19 ++-
1 file changed, 10 insertions(+), 9 deletions(-)
diff --git