On Wed, Feb 19, 2014 at 2:21 PM, Andy Shevchenko
andriy.shevche...@linux.intel.com wrote:
This patch converts descriptions of the structures defined in
linux/gpio_keys.h
to follow kernel-doc format.
There is no functional change.
Signed-off-by: Andy Shevchenko
Hi,
On Sat, Feb 22, 2014 at 10:44:06PM -0800, Dmitry Torokhov wrote:
Hi Marjus,
On Thu, Feb 20, 2014 at 05:21:51PM +0100, Markus Pargmann wrote:
This is a driver for the imx25 ADC/TSC module. It controls the
touchscreen conversion queue and creates a touchscreen input device.
The driver
From: Xianglong Du xianglong...@csr.com
commit a1a7521064428fc1cf8 moved to report EV_KEY event(KEY_POWER) instead of
reporting EV_PWR event(KEY_SUSPEND), but it didn't enable the capability, so
the KEY_POWER will not be reported to userspace by input core. this patch fixes
the issue.
On Mon, 2014-02-17 at 21:23 +0800, Daniel J Blueman wrote:
Across 5+ years of kernels, I've been seeing occasional (1-2 times per
day) key-stuck issues where eg a fn+delete combo repeats delete until
I press delete again. I've seen this happen with fn+ctrl+left, leaving
left held and likewise
From: Peter Jones pjo...@redhat.com
Some systems, such as EFI-based Apple systems, won't necessarily have an
i8042 to initialize. We shouldn't be printing an error message in this
case, since not detecting the chip is the correct behavior.
v2: Downgrade to pr_notice instead of pr_err.
On Tue, Feb 25, 2014 at 10:47 AM, Adam Jackson a...@redhat.com wrote:
From: Peter Jones pjo...@redhat.com
Some systems, such as EFI-based Apple systems, won't necessarily have an
i8042 to initialize. We shouldn't be printing an error message in this
case, since not detecting the chip is the
Delete an unused symbol and update copyright date.
Signed-off-by: Christopher Heiny che...@synaptics.com
Cc: Dmitry Torokhov dmitry.torok...@gmail.com
--
drivers/input/rmi4/rmi_f11.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/drivers/input/rmi4/rmi_f11.c
I forgot to mention that if the fix below is acceptable it
should be queued for 3.13-stable (older kernels are not
affected).
On 02/26/2014 04:51 PM, Fernando Luis Vázquez Cao wrote:
I noticed that after hot unplugging a Logitech unifying receiver
(drivers/hid/hid-logitech-dj.c) the kernel
I noticed that after hot unplugging a Logitech unifying receiver
(drivers/hid/hid-logitech-dj.c) the kernel would occasionally spew a
stack trace similar to this:
usb 1-1.1.2: USB disconnect, device number 7
WARNING: CPU: 0 PID: 2865 at fs/sysfs/group.c:216 device_del+0x40/0x1b0()
sysfs group
