From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: John Stultz <jstultz@google.com>, Guenter Roeck <linux@roeck-us.net>
Cc: Alessandro Zummo <a.zummo@towertech.it>,
Thomas Gleixner <tglx@linutronix.de>,
Stephen Boyd <sboyd@kernel.org>,
linux-rtc@vger.kernel.org, linux-kernel@vger.kernel.org,
Brian Norris <briannorris@chromium.org>
Subject: Re: [PATCH v2 0/2] rtc: alarmtimer: Use maximum alarm time offset
Date: Mon, 30 Oct 2023 02:00:43 +0100 [thread overview]
Message-ID: <202310300100434b7ed65b@mail.local> (raw)
In-Reply-To: <169862665994.296255.17369001298571068518.b4-ty@bootlin.com>
On 30/10/2023 01:44:55+0100, Alexandre Belloni wrote:
>
> On Fri, 15 Sep 2023 08:22:36 -0700, Guenter Roeck wrote:
> > Some userspace applications use timerfd_create() to request wakeups after
> > a long period of time. For example, a backup application may request a
> > wakeup once per week. This is perfectly fine as long as the system does
> > not try to suspend. However, if the system tries to suspend and the
> > system's RTC does not support the required alarm timeout, the suspend
> > operation will fail with an error such as
> >
> > [...]
>
> Applied, thanks!
>
> [1/2] rtc: Add API function to return alarm time bound by rtc limit
> commit: b0790dc7419f334574fc5416690913ab4c9e9ba5
> [2/2] rtc: alarmtimer: Use maximum alarm time offset
> commit: f628128dfe77f6e475507798b0f7ed25831ae893
>
Actually, this is already in tip but I didn't get the notification.
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2023-10-30 1:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-15 15:22 [PATCH v2 0/2] rtc: alarmtimer: Use maximum alarm time offset Guenter Roeck
2023-09-15 15:22 ` [PATCH v2 1/2] rtc: Add API function to return alarm time bound by rtc limit Guenter Roeck
2023-10-09 13:08 ` [tip: timers/core] rtc: Add API function to return alarm time bound by hardware limit tip-bot2 for Guenter Roeck
2023-09-15 15:22 ` [PATCH 2/2] rtc: alarmtimer: Use maximum alarm time offset Guenter Roeck
2023-09-15 17:42 ` John Stultz
2023-10-09 13:08 ` [tip: timers/core] alarmtimer: Use maximum alarm time for suspend tip-bot2 for Guenter Roeck
2023-10-30 0:44 ` [PATCH v2 0/2] rtc: alarmtimer: Use maximum alarm time offset Alexandre Belloni
2023-10-30 1:00 ` 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=202310300100434b7ed65b@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=a.zummo@towertech.it \
--cc=briannorris@chromium.org \
--cc=jstultz@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=sboyd@kernel.org \
--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 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.