From: Julien Grall <julien.grall@arm.com>
To: Stefano Stabellini <sstabellini@kernel.org>,
Jan Beulich <JBeulich@suse.com>
Cc: Lars Kurth <lars.kurth@citrix.com>, Wei Liu <wei.liu2@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: preparations for 4.9.2 and 4.7.5
Date: Mon, 12 Mar 2018 10:24:54 +0000 [thread overview]
Message-ID: <b8564eac-ced8-66f7-d66d-69eb74ce7bcd@arm.com> (raw)
In-Reply-To: <alpine.DEB.2.10.1803111345570.23583@sstabellini-ThinkPad-X260>
Hi,
On 11/03/18 20:48, Stefano Stabellini wrote:
> On Wed, 7 Mar 2018, Jan Beulich wrote:
>>>>> On 06.03.18 at 20:24, <sstabellini@kernel.org> wrote:
>>> On Tue, 6 Mar 2018, Jan Beulich wrote:
>>>> these stable releases should go out before the end of the month.
>>>> Please point out backport candidates you find missing from the
>>>> respective staging branches, but which you consider relevant.
>>>> Please note that 4.7.5 is expected to be the last xenproject.org
>>>> managed release from its branch.
>>>
>>> I am waiting for master to pass Julien's PSCI 1.1 series, then I intend
>>> to backport it to all stable trees (commits from
>>> f30b93b42b7137654a69676a61620f763c4ad3b3 to
>>> cd8b749282475caef095ea2f339a01d1ff9714ae).
>>>
>>> Backports to older trees might be difficult.
>>>
>>> Given your stable release plan, do you suggest I should start the
>>> backports now, even if master has not passed yet, or wait?
>>
>> There have been a lot of minor issues lately keeping pushes from
>> happening on master, so if the commits above have not been
>> pushed just because of such a glitch, I'd be fine with them being
>> backported right away. If, however, there's any doubt, then I'd
>> prefer if you waited. But in the end on the ARM side you know
>> better than me what's best.
>
> Master hasn't passed yet, so no backports of the ARM64 Spectre
> mitigation for the moment.
I really don't like the idea to ship 4.9.2 and 4.7.5 with broken arm64
spectre patches. This is indeed the case today as the previous series
was based on early discussion.
But unstable is blocked on amd64 patches. None of the arm64 spectre
series touch common code, so I am not sure what prevents us to backport
them.
> In the meantime, I tagged the QEMU trees. >
Cheers,
--
Julien Grall
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel
next prev parent reply other threads:[~2018-03-12 10:25 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-06 15:32 preparations for 4.9.2 and 4.7.5 Jan Beulich
2018-03-06 19:24 ` Stefano Stabellini
2018-03-07 7:35 ` Jan Beulich
2018-03-11 20:48 ` Stefano Stabellini
2018-03-12 10:24 ` Julien Grall [this message]
2018-03-12 10:27 ` Julien Grall
2018-03-15 0:36 ` Stefano Stabellini
2018-03-15 23:52 ` Stefano Stabellini
2018-03-16 11:15 ` Julien Grall
2018-03-16 16:33 ` Stefano Stabellini
2018-03-16 16:56 ` Julien Grall
2018-03-16 17:15 ` Julien Grall
2018-04-03 14:43 ` Julien Grall
2018-04-03 23:55 ` Stefano Stabellini
2018-04-04 8:59 ` Julien Grall
2018-04-04 9:37 ` Lars Kurth
2018-04-04 10:56 ` Lars Kurth
2018-04-04 21:02 ` Stefano Stabellini
2018-03-07 16:54 ` Wei Liu
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=b8564eac-ced8-66f7-d66d-69eb74ce7bcd@arm.com \
--to=julien.grall@arm.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=lars.kurth@citrix.com \
--cc=sstabellini@kernel.org \
--cc=wei.liu2@citrix.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 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.