All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@hp.com>
To: Simon Horman <horms@verge.net.au>
Cc: xen-devel@lists.xensource.com,
	Ian Campbell <Ian.Campbell@citrix.com>,
	xen-ia64-devel@lists.xensource.com
Subject: Re: [patch 0/3] xen: Extend xen kexec hypercall to return additional regions
Date: Thu, 28 Feb 2008 08:36:00 -0700	[thread overview]
Message-ID: <1204212960.24352.51.camel@bling> (raw)
In-Reply-To: <20080228033516.GA16840@verge.net.au>


On Thu, 2008-02-28 at 12:35 +0900, Simon Horman wrote:
> I'll come right out and say that I don't fancy this two stage .c
> indirectly including itself approach. And I hope this change can help us
> move away from there, as well as providing the functionality
> extendability that this patch set describes.

   Wow, that's pretty nasty.  Thanks for the explanation.

	Alex

-- 
Alex Williamson                             HP Open Source & Linux Org.

      parent reply	other threads:[~2008-02-28 15:36 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-27  7:01 [patch 0/3] xen: Extend xen kexec hypercall to return additional regions Simon Horman
2008-02-27  7:01 ` [patch 1/3] kexec: limit scope of the use of compat_kexec_range_t Simon Horman
2008-02-27  7:01 ` [patch 2/3] kexec: Add machine_kexec_get() Simon Horman
2008-02-27  7:01 ` [patch 3/3] kexec: extend hypercall for efi memory map, boot parameter and xenheap regions Simon Horman
2008-02-28  7:50   ` [Xen-ia64-devel] " Simon Horman
2008-02-27 19:55 ` [patch 0/3] xen: Extend xen kexec hypercall to return additional regions Alex Williamson
2008-02-28  3:35   ` Simon Horman
2008-02-28  8:55     ` Keir Fraser
2008-02-29  0:54       ` Simon Horman
2008-02-28 15:36     ` Alex Williamson [this message]

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=1204212960.24352.51.camel@bling \
    --to=alex.williamson@hp.com \
    --cc=Ian.Campbell@citrix.com \
    --cc=horms@verge.net.au \
    --cc=xen-devel@lists.xensource.com \
    --cc=xen-ia64-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.