From: Ian Campbell <ian.campbell@citrix.com>
To: "Luis R. Rodriguez" <mcgrof@suse.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Pry Mar <pryorm09@gmail.com>,
cfergeau@redhat.com, Jan Beulich <JBeulich@suse.com>,
Samuel Thibault <samuel.thibault@ens-lyon.org>
Subject: Re: [PATCH 0/9] xen: build fixes with gcc5 and binutils 2.25.0
Date: Tue, 9 Feb 2016 16:26:36 +0000 [thread overview]
Message-ID: <1455035196.19857.102.camel@citrix.com> (raw)
In-Reply-To: <20160209155615.GM25240@wotan.suse.de>
On Tue, 2016-02-09 at 16:56 +0100, Luis R. Rodriguez wrote:
>
> No you're right, this just fell through the cracks. The surprising case of
> things still being broken on modern tools however should raise a bit of
> concern either by opensuse factory folks or by Xen build folks in general.
AFAIK both Xen 4.6 and Xen unstable build fine with gcc5 now, and unstable
does so even with gcc6.
> The issues with required target platfroms to build and if developers are
> required to backport features for tools carried / forked is also a pretty
> important and IMHO a heavy requirement.
I'm not sure what this means, but Xen surely doesn't require anyone to
backport toolchains.
> > FWIW I would also suggest sending fixes to different components (qemu-xen,
> > qemu-xentraditional, xen.git, mini-os.git) as different series, lest
> > someone read patch #1 and assume the whole series is against that component
> > rather than something they maintain.
>
> OK thanks. Right Jan didn't read that cover letter so he was not ware of
> the work I put into vetting if things were upstream or not.
This seems like a non-sequitor compared to the paragraph quoted above it
(i.e. I'm not sure what upstream vs not has to do with sending unrelated
patches against different components in different series).
> > And BTW when we say to copy the maintainers we mean the person/people
> > responsible for the component in Xen, not the upstream maintainers,
> > e.g.
> > Stefano for qemu-xen not Peter Maydell. The xen.git MAINTAINERS file
> > lists
> > the right people.
>
> Sure, I do both though, first real upstream and then prod the Xen maintainers.
> I take it scripts/get_maintainer.pl should work though? I tried it in a few
> patches and it seemed to have worked
I wouldn't bet on it always doing the right thing with 3rd party components
like qemu-xen.
Ian.
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-02-09 16:26 UTC|newest]
Thread overview: 52+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-20 17:47 [PATCH 0/9] xen: build fixes with gcc5 and binutils 2.25.0 Luis R. Rodriguez
2015-11-20 17:47 ` [PATCH 1/9] Revert "Use the extra stack for 16bit USB and PS2 keyboard/mouse commands." Luis R. Rodriguez
2015-11-20 17:47 ` [PATCH 2/9] Use gnutls_priority_set_direct() to deprecate gnutls_*_set() Luis R. Rodriguez
2015-11-25 14:53 ` Konrad Rzeszutek Wilk
2015-11-25 19:36 ` [Xen-devel] " Luis R. Rodriguez
2015-11-25 20:44 ` Konrad Rzeszutek Wilk
2016-02-06 1:44 ` [Xen-devel] " Luis R. Rodriguez
2016-02-06 3:45 ` Konrad Rzeszutek Wilk
2016-02-06 4:03 ` Luis R. Rodriguez
2016-02-06 4:12 ` Konrad Rzeszutek Wilk
2016-02-06 4:36 ` Luis R. Rodriguez
2016-02-06 20:18 ` Doug Goldstein
2016-02-09 10:54 ` Jan Beulich
2016-02-09 15:46 ` [Xen-devel] " Luis R. Rodriguez
2016-02-09 16:06 ` Jan Beulich
2016-02-09 16:36 ` Olaf Hering
2016-02-09 16:42 ` [Xen-devel] " Luis R. Rodriguez
2016-02-09 18:23 ` Olaf Hering
2016-02-10 3:04 ` [Xen-devel] " Luis R. Rodriguez
2016-02-10 9:46 ` Ian Campbell
2016-02-10 15:41 ` [Xen-devel] " Luis R. Rodriguez
2016-02-10 15:44 ` Olaf Hering
2016-02-10 15:55 ` [Xen-devel] " Luis R. Rodriguez
2015-11-20 17:47 ` [PATCH 3/9] hw/usb-net.c: fix state check Luis R. Rodriguez
2015-11-20 17:47 ` [PATCH 4/9] qemu-xen-dir: spice: remove spice-experimental.h include Luis R. Rodriguez
2015-11-20 17:47 ` [PATCH 5/9] qemu-xen-dir: virtio-rng: fix check for period_ms validity Luis R. Rodriguez
2015-11-20 17:47 ` [PATCH 6/9] mini-os: fix linker warning with app.lds Luis R. Rodriguez
2015-11-20 17:47 ` [PATCH 7/9] stubdom: fix unfound libgmp library issues Luis R. Rodriguez
2015-11-20 17:47 ` [PATCH 8/9] vtpm: fix vtpmblk.c compilation warning Luis R. Rodriguez
2015-11-20 17:47 ` [PATCH 9/9] vtpm: guard against redefining TPM_VENDOR_COMMAND Luis R. Rodriguez
2016-02-06 1:48 ` [PATCH 0/9] xen: build fixes with gcc5 and binutils 2.25.0 Luis R. Rodriguez
2016-02-06 3:52 ` Konrad Rzeszutek Wilk
2016-02-06 4:07 ` Luis R. Rodriguez
2016-02-06 20:22 ` Doug Goldstein
2016-02-07 5:34 ` Fengguang Wu
2016-02-08 9:58 ` Ian Campbell
2016-02-09 15:56 ` Luis R. Rodriguez
2016-02-09 16:26 ` Ian Campbell [this message]
2016-02-09 16:39 ` Luis R. Rodriguez
2016-02-10 9:34 ` Ian Campbell
2016-02-09 8:08 ` Jan Beulich
2016-02-09 16:09 ` Luis R. Rodriguez
2016-02-09 16:22 ` Ian Campbell
2016-02-09 16:30 ` Luis R. Rodriguez
2016-02-09 16:39 ` Ian Campbell
2016-02-09 16:53 ` Luis R. Rodriguez
2016-02-10 5:21 ` Luis R. Rodriguez
2016-02-10 9:38 ` Ian Campbell
2016-02-10 5:44 ` Luis R. Rodriguez
2016-02-10 9:47 ` Ian Campbell
2016-02-11 8:08 ` Olaf Hering
2016-02-10 0:24 ` Dario Faggioli
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=1455035196.19857.102.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=JBeulich@suse.com \
--cc=cfergeau@redhat.com \
--cc=mcgrof@suse.com \
--cc=pryorm09@gmail.com \
--cc=samuel.thibault@ens-lyon.org \
--cc=xen-devel@lists.xensource.com \
/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 NNTP newsgroup(s).