From: John Stultz <john.stultz@linaro.org>
To: Borislav Petkov <bp@alien8.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
Jiri Kosina <jkosina@suse.cz>, Borislav Petkov <bp@suse.de>,
Thomas Gleixner <tglx@linutronix.de>,
Rabin Vincent <rabin.vincent@stericsson.com>
Subject: Re: [PATCH] RTC: Add an alarm disable quirk
Date: Mon, 22 Jul 2013 14:15:57 -0700 [thread overview]
Message-ID: <51EDA10D.6040207@linaro.org> (raw)
In-Reply-To: <20130722211223.GC4613@pd.tnic>
On 07/22/2013 02:12 PM, Borislav Petkov wrote:
> On Mon, Jul 22, 2013 at 01:59:01PM -0700, John Stultz wrote:
>> So did this work some of the time, but not all? Or was the behavior
>> totally unchanged with this?
> Yep, some of the time. The first couple of runs it worked and I was
> euphoric and then it rebooted and I almost threw the box out the window
> :-)
I can understand your frustration. :)
But its interesting it sort of worked, no? The bit you discovered
earlier with the dump_stack debugging call, where we're actually
disabling the irq twice was interesting.
If you use the debugging patch with this change, does it show any
different in logic between the working cases and the instant-reboot case?
thanks
-john
next prev parent reply other threads:[~2013-07-22 21:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-18 15:44 [PATCH] RTC: Add an alarm disable quirk Borislav Petkov
2013-07-18 16:35 ` John Stultz
2013-07-18 22:53 ` Borislav Petkov
2013-07-19 14:26 ` Borislav Petkov
2013-07-19 15:13 ` Borislav Petkov
2013-07-19 21:34 ` Borislav Petkov
2013-07-20 17:00 ` [PATCH -v2] " Borislav Petkov
2013-07-22 21:00 ` John Stultz
2013-07-22 21:19 ` Borislav Petkov
2013-07-22 22:03 ` John Stultz
2013-07-22 20:59 ` [PATCH] " John Stultz
2013-07-22 21:12 ` Borislav Petkov
2013-07-22 21:15 ` John Stultz [this message]
2013-07-22 21:27 ` Borislav Petkov
2013-07-22 22:17 ` John Stultz
2013-07-23 5:03 ` Borislav Petkov
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=51EDA10D.6040207@linaro.org \
--to=john.stultz@linaro.org \
--cc=bp@alien8.de \
--cc=bp@suse.de \
--cc=jkosina@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=rabin.vincent@stericsson.com \
--cc=tglx@linutronix.de \
/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