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]
Message-ID: <CAFLxGvzkfnLFJv+4AdsptU6+F4DMth0aa0OxBGzN8dQxau2G_Q@mail.gmail.com>
Date:	Sun, 31 May 2015 00:16:39 +0200
From:	Richard Weinberger <richard.weinberger@...il.com>
To:	Jan Kardell <jan.kardell@...liq.com>
Cc:	Alessandro Zummo <a.zummo@...ertech.it>,
	Alexandre Belloni <alexandre.belloni@...e-electrons.com>,
	rtc-linux@...glegroups.com, LKML <linux-kernel@...r.kernel.org>,
	Vincent Donnefort <vdonnefort@...il.com>,
	Dan Carpenter <dan.carpenter@...cle.com>, oen@...liq.com
Subject: Re: [PATCH v2] rtc: pcf8563 fix: return -EINVAL if we read an invalid time.

On Wed, May 27, 2015 at 2:48 PM, Jan Kardell <jan.kardell@...liq.com> wrote:
> Return -EINVAL if the voltage low bit is set to avoid getting a bogus
> time at boot.
> There was a comment stating that util-linux hwclock refuses to set a
> new time if we return an error code on read, but at least the current
> version do set the time as expected. Remove the comment and the check
> for valid time, and let the rtc core check it for us.
>
> Changes in v2: Remove the test for invalid time. Change dev_err to
> dev_info when voltage low is set.
>
> Signed-off-by: Jan Kardell <jan.kardell@...liq.com>
> ---
>  drivers/rtc/rtc-pcf8563.c | 9 ++-------
>  1 file changed, 2 insertions(+), 7 deletions(-)
>
> diff --git a/drivers/rtc/rtc-pcf8563.c b/drivers/rtc/rtc-pcf8563.c
> index 0ba7e59..6ce0a86 100644
> --- a/drivers/rtc/rtc-pcf8563.c
> +++ b/drivers/rtc/rtc-pcf8563.c
> @@ -22,7 +22,7 @@
>  #include <linux/of.h>
>  #include <linux/err.h>
>
> -#define DRV_VERSION "0.4.3"
> +#define DRV_VERSION "0.4.4"

Why do you need that?
Isn't the kernel version enough? :)

-- 
Thanks,
//richard
--
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