From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: Jerone Young <jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: [PATCH] Move x86 ioctl definitions from include/linux/kvm.h
Date: Fri, 30 Nov 2007 11:49:18 +0200 [thread overview]
Message-ID: <474FDC9E.2030701@qumranet.com> (raw)
In-Reply-To: <11955344663232-git-send-email-jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Jerone Young wrote:
> This patch is a continuation of the 7 patches sent earlier. This
> patch moves all x86 specific macros from include/linux/kvm.h to
> include/asm-x86/kvm.h.
>
>
Just noticed I'd dropped this old patch. Unfortunately kvm.git has
changed in this area. Care to re-spin?
Sorry about the drop.
--
Do not meddle in the internals of kernels, for they are subtle and quick to panic.
-------------------------------------------------------------------------
SF.Net email is sponsored by: The Future of Linux Business White Paper
from Novell. From the desktop to the data center, Linux is going
mainstream. Let it simplify your IT future.
http://altfarm.mediaplex.com/ad/ck/8857-50307-18918-4
next prev parent reply other threads:[~2007-11-30 9:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-20 4:54 [PATCH] Move x86 ioctl definitions from include/linux/kvm.h Jerone Young
[not found] ` <11955344663232-git-send-email-jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2007-11-20 8:34 ` Carsten Otte
2007-11-20 8:41 ` [PATCH] Move x86 ioctl definitions frominclude/linux/kvm.h Zhang, Xiantao
2007-11-30 9:49 ` Avi Kivity [this message]
[not found] ` <474FDC9E.2030701-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-11-30 16:21 ` [PATCH] Move x86 ioctl definitions from include/linux/kvm.h Jerone Young
2007-12-04 1:36 ` [PATCH] Move x86 ioctldefinitions " Zhang, Xiantao
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=474FDC9E.2030701@qumranet.com \
--to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
--cc=jyoung5-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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