All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dario Faggioli <dario.faggioli@citrix.com>
To: Jan Beulich <JBeulich@suse.com>,
	Anthony PERARD <anthony.perard@citrix.com>
Cc: xen-devel@lists.xenproject.org, Wei Liu <wei.liu2@citrix.com>
Subject: Re: [PATCH] Config.mk: update OVMF changeset
Date: Mon, 25 Sep 2017 16:20:32 +0200	[thread overview]
Message-ID: <1506349232.27663.5.camel@citrix.com> (raw)
In-Reply-To: <59C8CCFD020000780017F366@prv-mh.provo.novell.com>


[-- Attachment #1.1: Type: text/plain, Size: 775 bytes --]

On Mon, 2017-09-25 at 01:31 -0600, Jan Beulich wrote:
> > > > On 22.09.17 at 19:20, <anthony.perard@citrix.com> wrote:
> > 
> > Signed-off-by: Anthony PERARD <anthony.perard@citrix.com>
> 
> Would you mind clarifying in a brief description whether this is just
> routine catch up, or to bring in any specific changes we need?
> 
What we have right now, does not build, e.g., with gcc 7.2:

https://pastebin.com/xgeJHkdL

Which, I agree, should be mentioned/hinted at in the changelog.

Regards,
Dario
-- 
<<This happens because I choose it to happen!>> (Raistlin Majere)
-----------------------------------------------------------------
Dario Faggioli, Ph.D, http://about.me/dario.faggioli
Senior Software Engineer, Citrix Systems R&D Ltd., Cambridge (UK)

[-- Attachment #1.2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 127 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

  reply	other threads:[~2017-09-25 14:20 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-22 17:20 [PATCH] Config.mk: update OVMF changeset Anthony PERARD
2017-09-25  7:31 ` Jan Beulich
2017-09-25 14:20   ` Dario Faggioli [this message]
2017-09-26  9:52   ` [PATCH v2] " Anthony PERARD
2017-09-26 10:08     ` Wei Liu
  -- strict thread matches above, loose matches on Subject: below --
2020-08-12  9:55 [PATCH] " Wei Liu
2018-07-25 14:38 Anthony PERARD
2017-03-23 17:10 Anthony PERARD
2015-11-12 10:06 Wei Liu
2015-11-16 12:08 ` Ian Campbell
2015-11-16 12:10   ` Wei Liu
2015-10-14 11:41 Wei Liu
2015-10-22 15:55 ` Ian Campbell
2015-10-22 15:58   ` Ian Jackson
2015-10-22 16:02     ` Wei Liu
2015-10-22 16:09     ` Ian Campbell
2015-10-22 16:11       ` Stefano Stabellini
2015-10-22 17:08         ` Ian Jackson
2015-10-23  8:01           ` Jan Beulich
2015-10-23  9:11             ` Ian Campbell
2015-10-23 10:08               ` Stefano Stabellini
2015-10-23 11:18                 ` Ian Jackson
2015-10-23 11:38                   ` Stefano Stabellini
2015-10-23 11:56                     ` Ian Jackson
2015-10-23 11:52                   ` Jan Beulich
2015-10-23 12:16                   ` Ian Campbell
2015-10-23 12:43                     ` Stefano Stabellini
2015-10-23 12:56                       ` Ian Campbell
2015-10-23 13:16                         ` Fabio Fantoni
2015-10-23 13:38                           ` Ian Campbell
2013-12-08 20:50 Wei Liu
2013-12-09 11:04 ` George Dunlap
2013-12-09 11:10   ` Wei Liu
2013-12-09 11:17     ` George Dunlap
2013-12-09 11:33       ` Ian Campbell
2013-12-09 15:46       ` Ian Campbell

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=1506349232.27663.5.camel@citrix.com \
    --to=dario.faggioli@citrix.com \
    --cc=JBeulich@suse.com \
    --cc=anthony.perard@citrix.com \
    --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.