From: Cleber Rosa <crosa@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
qemu-devel@nongnu.org,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Max Reitz" <mreitz@redhat.com>
Subject: Re: [PATCH] virtiofs_submounts.py test: Note on vmlinuz param
Date: Mon, 15 Feb 2021 19:06:58 -0500 [thread overview]
Message-ID: <20210216000658.GB117147@localhost.localdomain> (raw)
In-Reply-To: <16a72cc1-1c92-287d-d4ad-043b425d3414@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1242 bytes --]
On Fri, Feb 12, 2021 at 09:42:24PM +0100, Philippe Mathieu-Daudé wrote:
> Hi Cleber,
> >
> > Hi Max,
> >
> > This looks good to me, and I've also tested your kernel build and
> > works like a charm.
> >
> > As further work on top of this, it may be beneficial to have test
> > documentation in a predictable place. The possibilities that come to
> > my mind:
> >
> > * docs/devel/testing.rst
> > * tests/acceptance/$test_file.py/data/README
> >
> > On a different topic, the "https://avocado-project.org/data/assets" has
> > enough bandwidth and can be used to hold this type asset.
>
> Can you define "this type asset" please?
>
Hi Phil,
Well, in this case I meant kernel/initrd builds, filesystem images, or
any other file that is used in such a test. But, I guess anything
generated from purely free software, with instructions on how to
reproduce it would be OK. The filesystem images there, for instance,
are generated by Avocado-VT unattended install tests.
Besides this server, there's another one that is being prepared,
provided by the fosshost that could be used for that sole purpose, and
be more closely attached to the QEMU project.
Anyway, just an idea...
Regards,
- Cleber.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-02-16 0:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-12 15:16 [PATCH] virtiofs_submounts.py test: Note on vmlinuz param Max Reitz
2021-02-12 18:58 ` Cleber Rosa
2021-02-12 20:42 ` Philippe Mathieu-Daudé
2021-02-16 0:06 ` Cleber Rosa [this message]
2021-02-18 16:24 ` Max Reitz
2021-02-12 20:58 ` Willian Rampazzo
2021-02-12 22:00 ` Alex Bennée
2021-02-16 0:00 ` Cleber Rosa
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=20210216000658.GB117147@localhost.localdomain \
--to=crosa@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=mreitz@redhat.com \
--cc=philmd@redhat.com \
--cc=qemu-devel@nongnu.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.