From: "Roger Pau Monné" <roger.pau@citrix.com>
To: Jan Beulich <jbeulich@suse.com>
Cc: xen-devel@lists.xenproject.org, committers@xenproject.org,
community.manager@xenproject.org,
Kelly Choi <kelly.choi@cloud.com>,
Oleksii <oleksii.kurochko@gmail.com>
Subject: Re: Xen 4.19 release status tracking list [ May ]
Date: Mon, 6 May 2024 12:34:54 +0200 [thread overview]
Message-ID: <ZjiyTp-1qKEOnGVN@macbook> (raw)
In-Reply-To: <a8be9d16-36e1-4528-b14c-42746bae605c@suse.com>
On Mon, May 06, 2024 at 11:35:00AM +0200, Jan Beulich wrote:
> On 06.05.2024 11:26, Roger Pau Monné wrote:
> > And then some patches that I don't expect to make progress:
> >
> > x86/shutdown: change default reboot method preference
> > https://lore.kernel.org/xen-devel/20230915074347.94712-1-roger.pau@citrix.com/
> >
> > x86/time: prefer CMOS over EFI_GET_TIME
> > https://lore.kernel.org/xen-devel/20240315114242.33309-1-roger.pau@citrix.com/
> >
> > I find it quite funny how everyone complains about all downstreams
> > carrying similar patches to deal with firmware bugs, yet when I
> > attempt to formally post them I get zero interest from such
> > downstreams. Maybe raising them here will help get some eyes.
>
> Well, as indicated on the Community Call I've meanwhile proposed a design
> session (which won't really be about design) for Lisbon, as to maintenance
> of our EFI interfacing. I think I had provided feedback on the shutdown
> patch, and I didn't think there was much of a point repeating almost the
> same for the time one.
I know you are likely not OK with those, so I wasn't expecting input
from you. We had discussions in the past where people complained that
our defaults are not OK because they lead to errors and panics on
production systems, and I'm surprised to find that none seem to have
cared about the above patches that attempt to address at least part of
this.
> As a minor remark on what you say above: It's clearly not "all"
> downstreams, as we don't carry anything similar to either of the two
> patches. But I'm pretty sure you meant "most" or "many" anyway.
Yes, indeed not all. I don't carry those either on the FreeBSD
packages.
Thanks, Roger.
prev parent reply other threads:[~2024-05-06 10:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-03 16:54 Xen 4.19 release status tracking list [ May ] Oleksii
2024-05-06 7:11 ` Jan Beulich
2024-05-06 8:25 ` Oleksii
2024-05-06 9:26 ` Roger Pau Monné
2024-05-06 9:35 ` Jan Beulich
2024-05-06 10:34 ` Roger Pau Monné [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=ZjiyTp-1qKEOnGVN@macbook \
--to=roger.pau@citrix.com \
--cc=committers@xenproject.org \
--cc=community.manager@xenproject.org \
--cc=jbeulich@suse.com \
--cc=kelly.choi@cloud.com \
--cc=oleksii.kurochko@gmail.com \
--cc=xen-devel@lists.xenproject.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 read-only IMAP folder(s) and NNTP newsgroup(s).