qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Cc: fam@euphon.net, berrange@redhat.com, f4bug@amsat.org,
	aurelien@aurel32.net, pbonzini@redhat.com, stefanha@redhat.com,
	crosa@redhat.com, "Alex Bennée" <alex.bennee@linaro.org>
Subject: [PATCH v1 for 7.2 0/9] test and doc updates
Date: Tue,  8 Nov 2022 09:22:59 +0000	[thread overview]
Message-ID: <20221108092308.1717426-1-alex.bennee@linaro.org> (raw)

Hi,

Its freeze o'clock so I'm reverting to collecting fixes for the tree.
Most of these patches have been posted before as single patch RFCs. A
couple are already scheduled through other trees so will drop out in
due course. The docs update has included some feedback for the review
and should be good for an rc1.

The following have not been reviewed:

 - hw/virtio: introduce virtio_device_should_start
 - tests/docker: allow user to override check target
 - tests/avocado: improve behaviour waiting for login prompts

Alex Bennée (7):
  tests/avocado: improve behaviour waiting for login prompts
  tests/docker: allow user to override check target
  hw/virtio: introduce virtio_device_should_start
  docs/devel: add a maintainers section to development process
  docs/devel: make language a little less code centric
  docs/devel: simplify the minimal checklist
  docs/devel: try and improve the language around patch review

Cédric Le Goater (1):
  tests/avocado/machine_aspeed.py: Reduce noise on the console for SDK
    tests

Stefan Weil (1):
  Run docker probe only if docker or podman are available

 docs/devel/code-of-conduct.rst           |   2 +
 docs/devel/index-process.rst             |   1 +
 docs/devel/maintainers.rst               | 106 +++++++++++++++++++++++
 docs/devel/submitting-a-patch.rst        | 101 +++++++++++++--------
 docs/devel/submitting-a-pull-request.rst |  12 +--
 configure                                |   2 +-
 include/hw/virtio/virtio.h               |  18 ++++
 hw/block/vhost-user-blk.c                |   6 +-
 hw/virtio/vhost-user-fs.c                |   2 +-
 hw/virtio/vhost-user-gpio.c              |   2 +-
 hw/virtio/vhost-user-i2c.c               |   2 +-
 hw/virtio/vhost-user-rng.c               |   2 +-
 hw/virtio/vhost-user-vsock.c             |   2 +-
 hw/virtio/vhost-vsock.c                  |   2 +-
 tests/avocado/avocado_qemu/__init__.py   |  89 ++++++++++++++++++-
 tests/avocado/machine_aspeed.py          |  17 ++--
 tests/docker/Makefile.include            |   2 +
 tests/docker/common.rc                   |   6 +-
 18 files changed, 309 insertions(+), 65 deletions(-)
 create mode 100644 docs/devel/maintainers.rst

-- 
2.34.1



             reply	other threads:[~2022-11-08  9:23 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-08  9:22 Alex Bennée [this message]
2022-11-08  9:23 ` [PATCH v1 1/9] Run docker probe only if docker or podman are available Alex Bennée
2022-11-08  9:23 ` [PATCH v1 2/9] tests/avocado: improve behaviour waiting for login prompts Alex Bennée
2022-11-08 11:23   ` Philippe Mathieu-Daudé
2022-11-08 21:19   ` John Snow
2022-11-08  9:23 ` [PATCH v1 3/9] tests/avocado/machine_aspeed.py: Reduce noise on the console for SDK tests Alex Bennée
2022-11-08  9:23 ` [PATCH v1 4/9] tests/docker: allow user to override check target Alex Bennée
2022-11-08 11:12   ` Philippe Mathieu-Daudé
2022-11-08  9:23 ` [PATCH v1 5/9] hw/virtio: introduce virtio_device_should_start Alex Bennée
2022-11-08  9:32   ` Michael S. Tsirkin
2022-11-08 10:23     ` Alex Bennée
2022-11-08 10:26       ` Michael S. Tsirkin
2022-11-08 11:21         ` Alex Bennée
2022-11-08 15:24           ` Michael S. Tsirkin
2022-11-08 16:41             ` Alex Bennée
2022-11-08  9:33   ` Michael S. Tsirkin
2022-11-14 16:18   ` Christian Borntraeger
2022-11-14 16:37     ` Michael S. Tsirkin
2022-11-14 16:55       ` Christian Borntraeger
2022-11-14 17:10         ` Michael S. Tsirkin
2022-11-14 17:15           ` Christian Borntraeger
2022-11-14 17:20             ` Michael S. Tsirkin
2022-11-15  7:44               ` Christian Borntraeger
2022-11-15  8:18               ` Christian Borntraeger
2022-11-15  9:05                 ` Michael S. Tsirkin
2022-11-15 11:25                 ` Michael S. Tsirkin
2022-11-15 13:25                   ` Christian Borntraeger
2022-11-15 14:31               ` Alex Bennée
2022-11-15 15:09                 ` Christian Borntraeger
2022-11-15 16:05                   ` Alex Bennée
2022-11-15 16:40                     ` Christian Borntraeger
2022-11-15 16:46                       ` Christian Borntraeger
2022-11-21 22:37                         ` Michael S. Tsirkin
2022-11-23  6:27                           ` Christian Borntraeger
2022-11-14 16:43     ` Alex Bennée
2022-11-08  9:23 ` [PATCH v1 6/9] docs/devel: add a maintainers section to development process Alex Bennée
2022-11-08  9:23 ` [PATCH v1 7/9] docs/devel: make language a little less code centric Alex Bennée
2022-11-08  9:23 ` [PATCH v1 8/9] docs/devel: simplify the minimal checklist Alex Bennée
2022-11-08  9:23 ` [PATCH v1 9/9] docs/devel: try and improve the language around patch review Alex Bennée

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=20221108092308.1717426-1-alex.bennee@linaro.org \
    --to=alex.bennee@linaro.org \
    --cc=aurelien@aurel32.net \
    --cc=berrange@redhat.com \
    --cc=crosa@redhat.com \
    --cc=f4bug@amsat.org \
    --cc=fam@euphon.net \
    --cc=pbonzini@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@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).