From: Thomas Gleixner <tglx@linutronix.de>
To: Michael Trimarchi <michael@amarulasolutions.com>
Cc: Michael <michael@mipisi.de>,
Alexandre Belloni <alexandre.belloni@bootlin.com>,
linux-rtc@vger.kernel.org, John Stultz <john.stultz@linaro.org>,
Stephen Boyd <sboyd@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: Problem when function alarmtimer_suspend returns 0 if time delta is zero
Date: Wed, 08 Feb 2023 19:06:11 +0100 [thread overview]
Message-ID: <87edr02fsc.ffs@tglx> (raw)
In-Reply-To: <Y+O+VBSNywC7LKhn@panicking>
Michael!
On Wed, Feb 08 2023 at 16:23, Michael Trimarchi wrote:
> On Wed, Sep 04, 2019 at 12:49:21AM +0200, Thomas Gleixner wrote:
>> On Tue, 3 Sep 2019, Michael wrote:
>> >
>> > thank you very much for your patch. Unfortunately currently I can only test it
>> > with a kernel 4.1.52 but i've tried to patch
>> > your new logic into my older kernel version.
>>
> Is this patch valid on mainline too? because apply it was let rtc
> working 100% of the time
I wrote that patch against the back then mainline code. No idea if it's
still applying, but the underlying issue is still the same AFAICT.
It needs some polishing and a proper changelog.
Thanks,
tglx
next prev parent reply other threads:[~2023-02-08 18:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <S1728511AbfHaSEm/20190831180442Z+580@vger.kernel.org>
2019-08-31 18:32 ` Problem when function alarmtimer_suspend returns 0 if time delta is zero Michael
2019-09-02 7:49 ` Alexandre Belloni
2019-09-02 10:57 ` Thomas Gleixner
2019-09-03 18:48 ` Michael
2019-09-03 22:49 ` Thomas Gleixner
2023-02-08 15:23 ` Michael Trimarchi
2023-02-08 18:06 ` Thomas Gleixner [this message]
2023-02-09 11:19 ` Michael Nazzareno Trimarchi
2023-02-09 15:40 ` Thomas Gleixner
2023-02-11 1:04 ` John Stultz
2023-02-11 1:18 ` John Stultz
2023-02-11 6:25 ` Michael Nazzareno Trimarchi
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=87edr02fsc.ffs@tglx \
--to=tglx@linutronix.de \
--cc=alexandre.belloni@bootlin.com \
--cc=john.stultz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=michael@amarulasolutions.com \
--cc=michael@mipisi.de \
--cc=sboyd@kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).