From: Jeremy Fitzhardinge <jeremy@goop.org>
To: James Morris <jmorris@redhat.com>
Cc: virtualization@lists.osdl.org
Subject: Re: [PATCH] paravirt build fix
Date: Wed, 01 Nov 2006 14:40:36 -0800 [thread overview]
Message-ID: <45492264.4040009@goop.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0611011724300.31378-100000@redline.boston.redhat.com>
James Morris wrote:
> Currently, 020-paravirt-xen.patch contains inconsistent declarations for a
> bunch of native_read/write functions. This patch updates the declarations
> to use unsigned long for register values.
>
> Signed-off-by: James Morris <jmorris@redhat.com>
>
Thanks. I'd already gone through and fixed those up locally, and was
about to push them out.
J
prev parent reply other threads:[~2006-11-01 22:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-01 22:28 [PATCH] paravirt build fix James Morris
2006-11-01 22:40 ` Jeremy Fitzhardinge [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=45492264.4040009@goop.org \
--to=jeremy@goop.org \
--cc=jmorris@redhat.com \
--cc=virtualization@lists.osdl.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 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).