From: Carsten Otte <cotte@de.ibm.com>
To: Hollis Blanchard <hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Subject: Re: [kvm-ppc-devel] [kvm-devel] [PATCH 1 of 3] Move address types
Date: Tue, 04 Dec 2007 13:35:23 +0000 [thread overview]
Message-ID: <4755579B.2060208@de.ibm.com> (raw)
In-Reply-To: <b4f32d68baf58bf071b2.1196717423@basalt>
Hollis Blanchard wrote:
> Signed-off-by: Hollis Blanchard <hollisb@us.ibm.com>
These types work for us too.
Acked-by: Carsten Otte <cotte@de.ibm.com>
-------------------------------------------------------------------------
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
_______________________________________________
kvm-ppc-devel mailing list
kvm-ppc-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/kvm-ppc-devel
WARNING: multiple messages have this Message-ID (diff)
From: Carsten Otte <cotte-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
To: Hollis Blanchard <hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
kvm-ppc-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Subject: Re: [PATCH 1 of 3] Move address types to their own header file
Date: Tue, 04 Dec 2007 14:35:23 +0100 [thread overview]
Message-ID: <4755579B.2060208@de.ibm.com> (raw)
In-Reply-To: <b4f32d68baf58bf071b2.1196717423@basalt>
Hollis Blanchard wrote:
> Signed-off-by: Hollis Blanchard <hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
These types work for us too.
Acked-by: Carsten Otte <cotte-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
-------------------------------------------------------------------------
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-12-04 13:35 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-03 21:30 [kvm-ppc-devel] [PATCH 0 of 3] Portability: allow for non-x86 Hollis Blanchard
2007-12-03 21:30 ` [PATCH 0 of 3] Portability: allow for non-x86 headers Hollis Blanchard
2007-12-03 21:30 ` [kvm-ppc-devel] [PATCH 1 of 3] Move address types to their own Hollis Blanchard
2007-12-03 21:30 ` [PATCH 1 of 3] Move address types to their own header file Hollis Blanchard
2007-12-04 13:35 ` Carsten Otte [this message]
2007-12-04 13:35 ` Carsten Otte
2007-12-03 21:30 ` [kvm-ppc-devel] [PATCH 2 of 3] Move IO device definitions to its Hollis Blanchard
2007-12-03 21:30 ` [PATCH 2 of 3] Move IO device definitions to its own header file Hollis Blanchard
2007-12-04 13:41 ` [kvm-ppc-devel] [kvm-devel] [PATCH 2 of 3] Move IO device Carsten Otte
2007-12-04 13:41 ` [PATCH 2 of 3] Move IO device definitions to its own header file Carsten Otte
[not found] ` <4755590F.60301-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
2007-12-04 14:58 ` [kvm-ppc-devel] [kvm-devel] [PATCH 2 of 3] Move IO Hollis Blanchard
2007-12-04 14:58 ` [kvm-ppc-devel] [PATCH 2 of 3] Move IO device definitions to its own header file Hollis Blanchard
2007-12-03 21:30 ` [kvm-ppc-devel] [PATCH 3 of 3] Stop including x86-specific headers Hollis Blanchard
2007-12-03 21:30 ` [PATCH 3 of 3] Stop including x86-specific headers in kvm_main.c Hollis Blanchard
2007-12-04 13:37 ` [kvm-ppc-devel] [kvm-devel] [PATCH 3 of 3] Stop including Carsten Otte
2007-12-04 13:37 ` [PATCH 3 of 3] Stop including x86-specific headers in kvm_main.c Carsten Otte
2007-12-05 10:14 ` [kvm-ppc-devel] [kvm-devel] [PATCH 0 of 3] Portability: allow Avi Kivity
2007-12-05 10:14 ` [PATCH 0 of 3] Portability: allow for non-x86 headers Avi Kivity
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=4755579B.2060208@de.ibm.com \
--to=cotte@de.ibm.com \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=kvm-ppc-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 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.