From: Keir Fraser <keir@xen.org>
To: Jan Beulich <JBeulich@novell.com>,
"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>
Subject: Re: [PATCH, RFC 0/5] various small improvements and cleanup
Date: Wed, 22 Dec 2010 13:25:48 +0000 [thread overview]
Message-ID: <C937ACDC.DADA%keir@xen.org> (raw)
In-Reply-To: <4D11F77302000078000294C3@vpn.id2.novell.com>
Yes, these all look fine to me. Actually I'm not sure whether we really need
a general-purpose sort (patch 1/5). But I suppose we could use it in places
like extable.c, so we might as well have it.
-- Keir
On 22/12/2010 12:04, "Jan Beulich" <JBeulich@novell.com> wrote:
> This patch set is only loosely connected (with the exception of the first
> two patches and some ordering dependencies to apply cleanly), and is
> known to apply only to c/s 22467. I'm posting in the hope to get
> eventual review comments in order to then possibly do a re-submission
> once the large set of changes currently pending in the staging tree
> passed regression testing.
>
> Patch 1/5: make sort() generally available
> Patch 2/5: x86-64: use PC-relative exception table entries
> Patch 3/5: x86: link time .data section adjustments
> Patch 4/5: x86: avoid unlikely taken forward branches
> Patch 5/5: use bool_t for various boolean variables
>
> Signed-off-by: Jan Beulich <jbeulich@novell.com>
>
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2010-12-22 13:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-22 12:04 [PATCH, RFC 0/5] various small improvements and cleanup Jan Beulich
2010-12-22 13:25 ` Keir Fraser [this message]
2010-12-22 13:29 ` Jan Beulich
2010-12-22 13:33 ` Keir Fraser
2010-12-22 13:49 ` Jan Beulich
2010-12-22 14:44 ` 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=C937ACDC.DADA%keir@xen.org \
--to=keir@xen.org \
--cc=JBeulich@novell.com \
--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.