From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>
Cc: qemu-devel@nongnu.org,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Thomas Huth" <thuth@redhat.com>, "Ed Maste" <emaste@freebsd.org>,
"Li-Wen Hsu" <lwhsu@freebsd.org>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH] tests: update lcitool to fix freebsd py311-yaml rename
Date: Mon, 14 Oct 2024 14:31:39 +0100 [thread overview]
Message-ID: <Zw0dO6tRQeGQRanI@redhat.com> (raw)
In-Reply-To: <CAFEAcA8oJvasajohf5BA1MehD0pvLWYdX=iV2fk_gJz=AU_WHQ@mail.gmail.com>
On Mon, Oct 14, 2024 at 02:26:28PM +0100, Peter Maydell wrote:
> On Mon, 14 Oct 2024 at 14:03, Daniel P. Berrangé <berrange@redhat.com> wrote:
> >
> > This addresses the py311-yaml -> py311-pyyaml rename in FreeBSD.
> >
> > The change to the OpenSUSE dockerfile is something that will allow
> > QEMU to access rust bindgen in future.
>
> That sounds like it should be in a separate patch?
No, it is all synced by the 'make lcitool-refresh' after updating
the submodule hash, so doesn't make sense to split.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2024-10-14 13:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-14 13:02 [PATCH] tests: update lcitool to fix freebsd py311-yaml rename Daniel P. Berrangé
2024-10-14 13:26 ` Peter Maydell
2024-10-14 13:31 ` Daniel P. Berrangé [this message]
2024-10-14 13:48 ` Thomas Huth
2024-10-14 16:05 ` Peter Maydell
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=Zw0dO6tRQeGQRanI@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=emaste@freebsd.org \
--cc=lwhsu@freebsd.org \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@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).