From: Andrea Bolognani <abologna@redhat.com>
To: Stefano Brivio <sbrivio@redhat.com>
Cc: passt-dev@passt.top
Subject: Re: [PATCH 0/5] qrap: Fix a number of issues
Date: Mon, 27 Feb 2023 05:59:04 -0800 [thread overview]
Message-ID: <CABJz62P-KXidyMnkwON-Ld1P-LUA-BXz0CbkLb8LyZP28X43Gg@mail.gmail.com> (raw)
In-Reply-To: <20230227112527.01af34d3@elisabeth>
On Mon, Feb 27, 2023 at 11:25:27AM +0100, Stefano Brivio wrote:
> If you think it's useful, by the way, feel free to submit those as a
> patch for something on the lines of "test/kubevirt/qrap-tests", with
> explicit licensing terms and something similar to your email as README.
>
> We wouldn't run them automatically, I'm not sure I would personally try
> them out, qrap should hopefully go away in a few months (even though
> KubeVirt YAMLs could still be helpful), and... I know it's effort, so
> I'm not really pushing for it, you know better.
I'm really counting on the next patch that touches qrap being the one
that gets rid of it for good :)
--
Andrea Bolognani / Red Hat / Virtualization
next prev parent reply other threads:[~2023-02-27 13:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-24 18:49 [PATCH 0/5] qrap: Fix a number of issues Andrea Bolognani
2023-02-24 18:49 ` [PATCH 1/5] qrap: Fix limits for PCI addresses Andrea Bolognani
2023-02-26 23:54 ` David Gibson
2023-02-24 18:49 ` [PATCH 2/5] qrap: Fix support for pc machines Andrea Bolognani
2023-02-26 23:55 ` David Gibson
2023-02-24 18:49 ` [PATCH 3/5] qrap: Drop args in JSON format Andrea Bolognani
2023-02-26 23:56 ` David Gibson
2023-02-24 18:49 ` [PATCH 4/5] qrap: Introduce machine-specific PCI address base Andrea Bolognani
2023-02-26 23:58 ` David Gibson
2023-02-24 18:49 ` [PATCH 5/5] qrap: Generate -netdev as JSON Andrea Bolognani
2023-02-27 0:00 ` David Gibson
2023-02-24 19:36 ` [PATCH 0/5] qrap: Fix a number of issues Andrea Bolognani
2023-02-27 10:25 ` Stefano Brivio
2023-02-27 13:59 ` Andrea Bolognani [this message]
2023-02-27 21:54 ` Stefano Brivio
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=CABJz62P-KXidyMnkwON-Ld1P-LUA-BXz0CbkLb8LyZP28X43Gg@mail.gmail.com \
--to=abologna@redhat.com \
--cc=passt-dev@passt.top \
--cc=sbrivio@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.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
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 IMAP folder(s).