kfree on a null pointer is a no-op. Hence null check is not
necessary.
Signed-off-by: Sachin Kamat sachin.ka...@linaro.org
---
drivers/input/touchscreen/edt-ft5x06.c |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/drivers/input/touchscreen/edt-ft5x06.c
'pdata' is already dereferenced earlier. Hence this check is
meaningless.
Signed-off-by: Sachin Kamat sachin.ka...@linaro.org
---
drivers/input/touchscreen/eeti_ts.c |3 +--
1 files changed, 1 insertions(+), 2 deletions(-)
diff --git a/drivers/input/touchscreen/eeti_ts.c
Hi Dmitry
On Thu, Mar 28, 2013 at 6:06 AM, Dmitry Torokhov
dmitry.torok...@gmail.com wrote:
On Thu, Mar 28, 2013 at 01:49:24AM +0100, David Herrmann wrote:
+ spin_lock_irq(dev-event_lock);
+ spin_lock(client-buffer_lock);
+
+ ret = bits_to_user(bits, max, size, p, compat);
This
Add match table for device tree binding and dts binding doc.
Signed-off-by: Mischa Jonker mjon...@synopsys.com
---
.../devicetree/bindings/serio/snps-arc_ps2.txt | 16
drivers/input/serio/arc_ps2.c | 14 --
2 files changed, 28
If userspace requests current KEY-state, they very likely assume that no
such events are pending in the output queue of the evdev device.
Otherwise, they will parse events which they already handled via
EVIOCGKEY(). For XKB applications this can cause irreversible keyboard
states if a modifier is