From: Thomas Huth <thuth@redhat.com>
To: Richard Henderson <rth@twiddle.net>,
qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/4] include/exec/poison: Add missing TARGET defines
Date: Tue, 20 Jun 2017 07:18:06 +0200 [thread overview]
Message-ID: <cfb64cc2-10ce-3e60-3b85-361d571112e2@redhat.com> (raw)
In-Reply-To: <7b5278e2-9624-2faa-b888-eaa23492c405@twiddle.net>
On 19.06.2017 23:49, Richard Henderson wrote:
> On 06/14/2017 12:21 PM, Thomas Huth wrote:
>> #pragma GCC poison TARGET_CRIS
>> #pragma GCC poison TARGET_LM32
>
> Missing HPPA and TILEGX.
Oh, looks like I missed the new defines from the -linux-user targets ...
thanks for the hint, I'll send a new version.
Thomas
next prev parent reply other threads:[~2017-06-20 5:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-14 19:21 [Qemu-devel] [PATCH 0/4] Poison some more target-specific defines Thomas Huth
2017-06-14 19:21 ` [Qemu-devel] [PATCH 1/4] include/exec/poison: Add missing TARGET defines Thomas Huth
2017-06-19 21:49 ` Richard Henderson
2017-06-20 5:18 ` Thomas Huth [this message]
2017-06-14 19:21 ` [Qemu-devel] [PATCH 2/4] include/exec/poison: Mark some CONFIG defines as poisoned, too Thomas Huth
2017-06-19 21:50 ` Richard Henderson
2017-06-14 19:21 ` [Qemu-devel] [PATCH 3/4] include/hw/i386/pc.h: Move CONFIG_KVM related definitions to kvm_i386.h Thomas Huth
2017-06-15 8:04 ` Paolo Bonzini
2017-06-14 19:21 ` [Qemu-devel] [PATCH 4/4] include/exec/poison: Mark CONFIG_KVM as poisoned, too Thomas Huth
2017-06-14 20:59 ` Paolo Bonzini
2017-06-15 8:32 ` Thomas Huth
2017-06-14 20:01 ` [Qemu-devel] [PATCH 0/4] Poison some more target-specific defines no-reply
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=cfb64cc2-10ce-3e60-3b85-361d571112e2@redhat.com \
--to=thuth@redhat.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).