From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Mario Limonciello <mario.limonciello@amd.com>
Cc: Pavel Machek <pavel@ucw.cz>,
Alessandro Zummo <a.zummo@towertech.it>,
"open list:REAL TIME CLOCK (RTC) SUBSYSTEM"
<linux-rtc@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>,
alvin.zhuge@gmail.com, renzhamin@gmail.com, kelvie@kelvie.ca,
Raul Rangel <rrangel@google.com>
Subject: Re: [PATCH] rtc: cmos: Use ACPI alarm for non-Intel x86 systems too
Date: Fri, 17 Nov 2023 23:57:05 +0100 [thread overview]
Message-ID: <2023111722570552652970@mail.local> (raw)
In-Reply-To: <5029e355-6fe8-4d48-9bc3-20256adfbdb7@amd.com>
On 14/11/2023 18:15:02-0600, Mario Limonciello wrote:
> On 11/14/2023 16:28, Alexandre Belloni wrote:
> > On 14/11/2023 10:06:36+0100, Pavel Machek wrote:
> > > On Mon 2023-11-13 23:38:19, Alexandre Belloni wrote:
> > > > On 13/11/2023 15:36:28-0600, Mario Limonciello wrote:
> > > > > Now that the merge window is over, can this be picked up?
> > > > >
> > > >
> > > > I'd be happy to invoice AMD so they get a quick response time.
> > >
> > > That is a really bad joke.
> >
> > Why would it be a joke?
> >
> > From what I get this is an issue since 2021, I don't get how this is so
> > urgent that I get a ping less than 24h after the end of the merge
> > window.
>
> It's possibly longer; but I don't have a large enough sample to say that
> it's safe that far back.
Would this help this one:
https://bugzilla.kernel.org/show_bug.cgi?id=68331
--
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2023-11-17 22:57 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-06 16:23 [PATCH] rtc: cmos: Use ACPI alarm for non-Intel x86 systems too Mario Limonciello
2023-11-06 16:17 ` Raul Rangel
2023-11-13 21:36 ` Mario Limonciello
2023-11-13 22:38 ` Alexandre Belloni
2023-11-14 9:06 ` Pavel Machek
2023-11-14 22:28 ` Alexandre Belloni
2023-11-15 0:15 ` Mario Limonciello
2023-11-17 22:57 ` Alexandre Belloni [this message]
2023-11-17 23:00 ` Mario Limonciello
2023-11-17 23:43 ` Raul Rangel
2023-11-17 17:36 ` 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=2023111722570552652970@mail.local \
--to=alexandre.belloni@bootlin.com \
--cc=a.zummo@towertech.it \
--cc=alvin.zhuge@gmail.com \
--cc=kelvie@kelvie.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rtc@vger.kernel.org \
--cc=mario.limonciello@amd.com \
--cc=pavel@ucw.cz \
--cc=renzhamin@gmail.com \
--cc=rrangel@google.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.