From: Avi Kivity <avi-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Christian Borntraeger
<borntraeger-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
Cc: Ehrhardt Christian
<ehrhardt-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org>,
kvm-ppc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
kvm-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org,
cotte-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org
Subject: Re: [PATCH] kvm-userspace: add ibm archs to unifdef header
Date: Tue, 04 Nov 2008 15:10:57 +0200 [thread overview]
Message-ID: <491049E1.4000204@redhat.com> (raw)
In-Reply-To: <200811041253.04465.borntraeger-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
Christian Borntraeger wrote:
> Am Montag, 3. November 2008 schrieb Ehrhardt Christian:
>
>> +#ifdef __s390__
>> +#ifndef CONFIG_S390
>> +#define CONFIG_S390 1
>> +#endif
>> +#endif
>> +
>> +#endif
>>
>>
>
> It seems that currently no header needs this, but better save than sorry.
>
> __s390__ is defined by gcc for s390 and s390x, CONFIG_S390 is set on s390 and
> s390x in the kernel config. This looks right.
>
Okay, applied. Thanks.
--
error compiling committee.c: too many arguments to function
--
To unsubscribe from this list: send the line "unsubscribe kvm-ppc" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2008-11-04 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 17:15 [PATCH] kvm-userspace: add ibm archs to unifdef header Ehrhardt Christian
2008-11-04 10:13 ` Avi Kivity
2008-11-04 11:53 ` Christian Borntraeger
[not found] ` <200811041253.04465.borntraeger-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org>
2008-11-04 13:10 ` Avi Kivity [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=491049E1.4000204@redhat.com \
--to=avi-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=borntraeger-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org \
--cc=cotte-tA70FqPdS9bQT0dZR+AlfA@public.gmane.org \
--cc=ehrhardt-23VcF4HTsmIX0ybBhKVfKdBPR1lH4CV8@public.gmane.org \
--cc=hollisb-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
--cc=kvm-ppc-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=kvm-u79uwXL29TY76Z2rM5mHXA@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