All of lore.kernel.org
 help / color / mirror / Atom feed
From: Keir Fraser <keir@xen.org>
To: "Roger Pau Monné" <roger.pau@entel.upc.edu>
Cc: xen-devel@lists.xensource.com
Subject: Re: [PATCH] ipxe: fix compilation issues with some gcc versions
Date: Sun, 18 Dec 2011 14:56:02 +0000	[thread overview]
Message-ID: <CB13AF82.3631C%keir@xen.org> (raw)
In-Reply-To: <CAPLaKK6Bv4f605TruaU8JCnBSWeBVg4o7q+o4Pwp1XVmk-GQdg@mail.gmail.com>

On 18/12/2011 13:26, "Roger Pau Monné" <roger.pau@entel.upc.edu> wrote:

> 2011/12/16 Keir Fraser <keir@xen.org>:
>> Perhaps we should pick a recent commit hash to clone, then? There's plenty
>> going on in there development-wise, which would surely have warranted a
>> release or two; it just looks like they couldn't be arsed to tag releases.
>> Hanging on to a two-year-old version and building up a backport queue
>> doesn't make sense. At the very least we should do this in xen-unstable, and
>> get some testing done of recent ipxe upstream.
> 
> That's fine, I agree that we should pick a most recent ipxe version
> for unstable, if not things like this are going to happen every now
> and then and we will end up with a massive queue of patches. But in
> the meantime, is it possible to apply this patch to xen-4.1 and
> possibly xen-4.0?

Done for 4.1. In 4.0 it looks like we have the generated code checked in, so
this fix is not necessary there.

 -- Keir

> Thanks, Roger.

  reply	other threads:[~2011-12-18 14:56 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-16 12:50 [PATCH] ipxe: fix compilation issues with some gcc versions Roger Pau Monne
2011-12-16 12:59 ` Keir Fraser
2011-12-16 13:04   ` Roger Pau Monné
2011-12-16 13:21     ` Keir Fraser
2011-12-18 13:26       ` Roger Pau Monné
2011-12-18 14:56         ` Keir Fraser [this message]
2011-12-20 12:57           ` Roger Pau Monné
2011-12-20 13:02             ` Keir Fraser

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=CB13AF82.3631C%keir@xen.org \
    --to=keir@xen.org \
    --cc=roger.pau@entel.upc.edu \
    --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 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.