From: Jan Beulich <jbeulich@suse.com>
To: Ian Jackson <iwj@xenproject.org>
Cc: Andrew Cooper <andrew.cooper3@citrix.com>,
Dario Faggioli <dfaggioli@suse.com>,
Julien Grall <julien@xen.org>,
community.manager@xenproject.org, committers@xenproject.org,
xen-devel@lists.xenproject.org
Subject: Re: [ANNOUNCE] Xen 4.15 - call for notification/status of significant bugs
Date: Fri, 5 Feb 2021 16:33:24 +0100 [thread overview]
Message-ID: <361da489-25a1-4a36-b917-9a092900b2e5@suse.com> (raw)
In-Reply-To: <24603.58528.901884.980466@mariner.uk.xensource.com>
On 04.02.2021 13:12, Ian Jackson wrote:
> Although there are a few things outstanding, we are now firmly into
> the bugfixing phase of the Xen 4.15 release.
>
> I searched my email (and my memory) and found four open blockers which
> I have listed below, and one closed blocker.
>
> I feel there are probably more issues out there, so please let me
> know, in response to this mail, of any other significant bugs you are
> aware of.
>
> Ian.
>
>
> OPEN ISSUES
> -----------
Roger has just pointed out to me that I should probably ask for
"x86/time: calibration rendezvous adjustments" to also be tracked
here. Though just to clarify - the bad behavior has been there
for a (long) while, so this isn't like a recent regression.
Jan
prev parent reply other threads:[~2021-02-05 15:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 15:33 [ANNOUNCE] Xen 4.15 release schedule - feature freeze now in effect Ian Jackson
2021-02-04 12:12 ` [ANNOUNCE] Xen 4.15 - call for notification/status of significant bugs Ian Jackson
2021-02-04 12:20 ` Andrew Cooper
2021-02-04 15:15 ` Ian Jackson
2021-02-04 14:20 ` Dario Faggioli
2021-02-04 15:00 ` Tamas K Lengyel
2021-02-04 18:22 ` Dario Faggioli
2021-02-04 15:12 ` Ian Jackson
2021-02-04 14:30 ` Jan Beulich
2021-02-04 15:18 ` Ian Jackson
2021-02-05 15:33 ` Jan Beulich [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=361da489-25a1-4a36-b917-9a092900b2e5@suse.com \
--to=jbeulich@suse.com \
--cc=andrew.cooper3@citrix.com \
--cc=committers@xenproject.org \
--cc=community.manager@xenproject.org \
--cc=dfaggioli@suse.com \
--cc=iwj@xenproject.org \
--cc=julien@xen.org \
--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 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.