From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: Jan Kardell <jan.kardell@telliq.com>,
Alessandro Zummo <a.zummo@towertech.it>,
rtc-linux@googlegroups.com, LKML <linux-kernel@vger.kernel.org>,
Vincent Donnefort <vdonnefort@gmail.com>,
Dan Carpenter <dan.carpenter@oracle.com>,
oen@telliq.com
Subject: Re: [rtc-linux] Re: [PATCH v2] rtc: pcf8563 fix: return -EINVAL if we read an invalid time.
Date: Sun, 31 May 2015 00:21:42 +0200 [thread overview]
Message-ID: <20150530222142.GM2185@piout.net> (raw)
In-Reply-To: <CAFLxGvzkfnLFJv+4AdsptU6+F4DMth0aa0OxBGzN8dQxau2G_Q@mail.gmail.com>
On 31/05/2015 at 00:16:39 +0200, Richard Weinberger wrote :
> On Wed, May 27, 2015 at 2:48 PM, Jan Kardell <jan.kardell@telliq.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@telliq.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? :)
>
That's also what I'm thinking but I don't care enough to ask people to
remove those.
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-05-30 22:21 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 12:48 [rtc-linux] [PATCH v2] rtc: pcf8563 fix: return -EINVAL if we read an invalid time Jan Kardell
2015-05-27 12:48 ` Jan Kardell
2015-05-27 18:53 ` [rtc-linux] " Alexandre Belloni
2015-05-27 18:53 ` Alexandre Belloni
2015-05-28 6:40 ` [rtc-linux] " Jan Kardell
2015-05-28 6:40 ` Jan Kardell
2015-05-30 22:16 ` [rtc-linux] " Richard Weinberger
2015-05-30 22:16 ` Richard Weinberger
2015-05-30 22:21 ` Alexandre Belloni [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150530222142.GM2185@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=a.zummo@towertech.it \
--cc=dan.carpenter@oracle.com \
--cc=jan.kardell@telliq.com \
--cc=linux-kernel@vger.kernel.org \
--cc=oen@telliq.com \
--cc=richard.weinberger@gmail.com \
--cc=rtc-linux@googlegroups.com \
--cc=vdonnefort@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.