From: Richard Henderson <richard.henderson@linaro.org>
To: Thomas Huth <thuth@redhat.com>, Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org,
"Daniel P . Berrange" <berrange@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [PATCH 2/3] capstone: Allow version 3.0.5 again
Date: Mon, 16 May 2022 22:35:07 -0700 [thread overview]
Message-ID: <f045022f-89fb-2f9d-6fa7-aba35fec0529@linaro.org> (raw)
In-Reply-To: <f8cd57a9-d560-b483-c9ff-8ffde755e80e@redhat.com>
On 5/16/22 12:22, Thomas Huth wrote:
> So it seems like really only the capstone 3.0.4 from Ubuntu 18.04 is broken,
> while this compiles fine with the capstone 3.0.5 from Ubuntu 20.04.
>
> I think my patches should be ok to apply now that we dropped support
> for Ubuntu 18.04.
Yes, I think so. Especially with the >=3.0.5 test.
r~
next prev parent reply other threads:[~2022-05-17 5:36 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 14:58 [RFC PATCH 0/3] Allow Capstone 3.0.5 again and remove the submodule Thomas Huth
2022-05-16 14:58 ` [PATCH 1/3] tests/vm: Add capstone to the NetBSD and OpenBSD VMs Thomas Huth
2022-05-17 5:37 ` Richard Henderson
2022-05-16 14:58 ` [PATCH 2/3] capstone: Allow version 3.0.5 again Thomas Huth
2022-05-16 15:46 ` Peter Maydell
2022-05-16 16:46 ` Richard Henderson
2022-05-16 16:53 ` Peter Maydell
2022-05-16 19:14 ` Richard Henderson
2022-05-16 19:22 ` Thomas Huth
2022-05-17 5:35 ` Richard Henderson [this message]
2022-05-17 5:40 ` Richard Henderson
2022-05-16 14:58 ` [PATCH 3/3] capstone: Remove the capstone submodule Thomas Huth
2022-05-17 5:42 ` Richard Henderson
2022-05-19 11:41 ` Peter Maydell
2022-05-23 12:15 ` Thomas Huth
2022-06-03 0:03 ` Richard Henderson
2022-06-03 0:56 ` Richard Henderson
2022-06-03 5:21 ` Thomas Huth
2022-06-03 13:48 ` Richard Henderson
2022-06-03 15:05 ` Thomas Huth
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=f045022f-89fb-2f9d-6fa7-aba35fec0529@linaro.org \
--to=richard.henderson@linaro.org \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/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).