From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Arnaud Ebalard <arno@natisbad.org>
Cc: rtc-linux@googlegroups.com, Jason Cooper <jason@lakedaemon.net>,
Sudeep Holla <Sudeep.Holla@arm.com>
Subject: [rtc-linux] Re: Intersil ISL12057 driver
Date: Thu, 24 Mar 2016 23:52:51 +0100 [thread overview]
Message-ID: <20160324225251.GK2570@piout.net> (raw)
In-Reply-To: <87lh57ldgv.fsf@natisbad.org>
Hi,
On 24/03/2016 at 23:26:24 +0100, Arnaud Ebalard wrote :
> 1) Handling of the century bit
>
This indeed needs fixing and it is quite simple. Do you care sending a
patch?
> 2) Alarm:
>
[...]
Well, my bad, your analysis is correct and I was thinking
8bc2a40730ec74271a0573a6882871308d069f5d was in 4.5 but it will actually
be in 4.6:
http://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=8bc2a40730ec74271a0573a6882871308d069f5d
This should solve that one. And you are right, I should probably do
something more generic in the framework to handle "wakeup-source".
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
--
--
You received this message because you are subscribed to "rtc-linux".
Membership options at http://groups.google.com/group/rtc-linux .
Please read http://groups.google.com/group/rtc-linux/web/checklist
before submitting a driver.
---
You received this message because you are subscribed to the Google Groups "rtc-linux" group.
To unsubscribe from this group and stop receiving emails from it, send an email to rtc-linux+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
next prev parent reply other threads:[~2016-03-24 22:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-23 17:10 [rtc-linux] Intersil ISL12057 driver Alexandre Belloni
2016-03-23 21:14 ` [rtc-linux] " Arnaud Ebalard
2016-03-24 22:26 ` Arnaud Ebalard
2016-03-24 22:52 ` Alexandre Belloni [this message]
2016-03-25 21:58 ` Arnaud Ebalard
2016-03-25 22:17 ` Alexandre Belloni
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=20160324225251.GK2570@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=Sudeep.Holla@arm.com \
--cc=arno@natisbad.org \
--cc=jason@lakedaemon.net \
--cc=rtc-linux@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox