From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Joe Lawrence <joe.lawrence@stratus.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
rtc-linux@googlegroups.com,
Alessandro Zummo <a.zummo@towertech.it>
Subject: [rtc-linux] Re: __rtc_read_alarm missing month/year field bug?
Date: Tue, 19 Jul 2016 12:49:58 +0200 [thread overview]
Message-ID: <20160719104958.GF7132@piout.net> (raw)
In-Reply-To: <57716404.9080204@stratus.com>
On 27/06/2016 at 13:36:04 -0400, Joe Lawrence wrote :
> Ping? This isn't a major problem, but can setup endless RTC interrupts
> under certain conditions on said hardware.
>
Well like said in my previous mail, I don't think the rollover is the
issue here but I'm interested in knowing what conditions are leading to
endless interrupts.
--
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel 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.
WARNING: multiple messages have this Message-ID (diff)
From: Alexandre Belloni <alexandre.belloni@free-electrons.com>
To: Joe Lawrence <joe.lawrence@stratus.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
rtc-linux@googlegroups.com,
Alessandro Zummo <a.zummo@towertech.it>
Subject: Re: __rtc_read_alarm missing month/year field bug?
Date: Tue, 19 Jul 2016 12:49:58 +0200 [thread overview]
Message-ID: <20160719104958.GF7132@piout.net> (raw)
In-Reply-To: <57716404.9080204@stratus.com>
On 27/06/2016 at 13:36:04 -0400, Joe Lawrence wrote :
> Ping? This isn't a major problem, but can setup endless RTC interrupts
> under certain conditions on said hardware.
>
Well like said in my previous mail, I don't think the rollover is the
issue here but I'm interested in knowing what conditions are leading to
endless interrupts.
--
Alexandre Belloni, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-07-19 10:50 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-20 16:06 [rtc-linux] __rtc_read_alarm missing month/year field bug? Joe Lawrence
2016-06-20 16:06 ` Joe Lawrence
2016-06-27 17:36 ` [rtc-linux] " Joe Lawrence
2016-06-27 17:36 ` Joe Lawrence
2016-07-19 10:49 ` Alexandre Belloni [this message]
2016-07-19 10:49 ` Alexandre Belloni
2016-07-21 19:52 ` [rtc-linux] " Joe Lawrence
2016-07-21 19:52 ` Joe Lawrence
2016-07-19 10:46 ` [rtc-linux] " Alexandre Belloni
2016-07-19 10:46 ` 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=20160719104958.GF7132@piout.net \
--to=alexandre.belloni@free-electrons.com \
--cc=a.zummo@towertech.it \
--cc=joe.lawrence@stratus.com \
--cc=linux-kernel@vger.kernel.org \
--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 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.