All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Jackson <iwj@xenproject.org>
To: Elliott Mitchell <ehem+xen@m5p.com>
Cc: Julien Grall <julien@xen.org>, Jan Beulich <jbeulich@suse.com>,
	"xen-devel\@lists.xenproject.org"
	<xen-devel@lists.xenproject.org>,
	Bertrand Marquis <bertrand.marquis@arm.com>,
	ba1020@protonmail.ch
Subject: Re: Tools backport request for Xen 4.14
Date: Mon, 9 Nov 2020 18:03:17 +0000	[thread overview]
Message-ID: <24489.33893.98470.334969@mariner.uk.xensource.com> (raw)
In-Reply-To: <20201009184930.GA65219@mattapan.m5p.com>

Elliott Mitchell writes ("Re: Tools backport request for Xen 4.14"):
> On Fri, Oct 09, 2020 at 06:47:22PM +0100, Julien Grall wrote:
> > Would it be possible to consider backporting to 4.14 the following tools 
> > commit:
> > 
> > d25cc3ec93eb "libxl: workaround gcc 10.2 maybe-uninitialized warning"
> > 
> > This would help to build Xen tools on Debian Testing with GCC 10. I 
> > haven't build itself myself, so I can't promise this is only one :).
> 
> >From Debian's repository:
> https://salsa.debian.org/xen-team/debian-xen.git
> 
> The master and knorrie/4.14 branches include that commit.  They will
> hopefully soon include all the Debian-specific bits for cross-building
> too.

I have now backported all of the GCC10 fixes to all the supported Xen
branches (ie back to 4.12).  Upstream staging-* now builds on Debian
sid, for me.  Sorry for not getting to this earlier.

Ian.


  reply	other threads:[~2020-11-09 18:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-09 17:47 Tools backport request for Xen 4.14 Julien Grall
2020-10-09 18:49 ` Elliott Mitchell
2020-11-09 18:03   ` Ian Jackson [this message]
2020-11-09 18:47     ` Olaf Hering
2020-11-10  7:47     ` Jan Beulich

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=24489.33893.98470.334969@mariner.uk.xensource.com \
    --to=iwj@xenproject.org \
    --cc=ba1020@protonmail.ch \
    --cc=bertrand.marquis@arm.com \
    --cc=ehem+xen@m5p.com \
    --cc=jbeulich@suse.com \
    --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.