lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Tue, 02 Sep 2014 09:43:34 +0200
From:	Daniel Mack <zonque@...il.com>
To:	Klaus Goger <klaus.goger@...obroma-systems.com>,
	Dmitry Torokhov <dmitry.torokhov@...il.com>
CC:	linux-input@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Input: cap1106 - fix register definition

On 09/02/2014 08:32 AM, Klaus Goger wrote:
> Use the correct register address for Calibration Active and Interrupt
> Enable
> 
> Signed-off-by: Klaus Goger <klaus.goger@...obroma-systems.com>

These register definitions are currently unused, but your fix is
correct. Just curious - are you planning to send patches that make use
of them?

  Acked-by: Daniel Mack <zonque@...il.com>


Thanks,
Daniel

> ---
>  drivers/input/keyboard/cap1106.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/input/keyboard/cap1106.c b/drivers/input/keyboard/cap1106.c
> index 180b184..d70b65a 100644
> --- a/drivers/input/keyboard/cap1106.c
> +++ b/drivers/input/keyboard/cap1106.c
> @@ -33,8 +33,8 @@
>  #define CAP1106_REG_SENSOR_CONFIG	0x22
>  #define CAP1106_REG_SENSOR_CONFIG2	0x23
>  #define CAP1106_REG_SAMPLING_CONFIG	0x24
> -#define CAP1106_REG_CALIBRATION		0x25
> -#define CAP1106_REG_INT_ENABLE		0x26
> +#define CAP1106_REG_CALIBRATION		0x26
> +#define CAP1106_REG_INT_ENABLE		0x27
>  #define CAP1106_REG_REPEAT_RATE		0x28
>  #define CAP1106_REG_MT_CONFIG		0x2a
>  #define CAP1106_REG_MT_PATTERN_CONFIG	0x2b
> 

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ