Re: preparations for 4.13.1 and 4.12.3

[Julien Grall <julien@xxxxxxx>]

Hi Stefano,

On 10/04/2020 17:37, Stefano Stabellini wrote:
> On Fri, 10 Apr 2020, Julien Grall wrote:
> > On 09/04/2020 08:41, Jan Beulich wrote:
> > > All,
> > Hi Jan & Stefano,
> >
> > > the releases are due in a week or two. Please point out backports
> > > you find missing from the respective staging branches, but which
> > > you consider relevant. (Ian, I notice there haven't been any
> > > tools side backports at all so far. Julien, Stefano - same for
> > > Arm.)
> > Below a list of suggested backport for Arm for 4.12 and 4.13:
> >
> > b4637ed6cd5375f04ac51d6b900a9ccad6c6c03a  xen/arm: initialize vpl011 flag
> > register
> > b31666c8912bf18d9eff963b06d856e7e818ff34  xen/arm: during efi boot, improve
> > the check for usable memory
> > f14f55b7ee295277c8dd09e37e0fa0902ccf7eb4  xen/arm: remove physical timer
> > offset
> > 3c601c5f056fba055b7a1438b84b69fc649275c3  xen/arm: Sign extend TimerValue when
> > computing the CompareValue
>
> Thanks! I did these four and also the following:
>
> 69da7d5440c609c57c5bba9a73b91c62ba2852e6 xen/arm: Handle unimplemented VGICv3 
> registers as RAZ/WI
I saw it and forgot to add it in the list :$.

> Jan,
>
> I think the following could be a good candidate. It also touches x86 so
> I thought I should ask you.
>
> 6827bea2b3b99153821b8b7446bdced27f720188 dom0-build: fix build with clang5
If we are backporting build fixes for newer compilers, shouldn't we 
backport all of them?
Cheers,

--
Julien Grall