qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: richard.henderson@linaro.org
Subject: [PULL 0/2] QAPI patches patches for 2024-07-29
Date: Mon, 29 Jul 2024 08:37:20 +0200	[thread overview]
Message-ID: <20240729063722.839708-1-armbru@redhat.com> (raw)

The following changes since commit 93b799fafd9170da3a79a533ea6f73a18de82e22:

  Merge tag 'pull-ppc-for-9.1-2-20240726-1' of https://gitlab.com/npiggin/qemu into staging (2024-07-26 15:10:45 +1000)

are available in the Git repository at:

  https://repo.or.cz/qemu/armbru.git tags/pull-qapi-2024-07-29

for you to fetch changes up to bc2e34e343b40b83cca82409db9c126df2e28c81:

  qapi/machine: Belatedly document target loongarch64 is since 7.1 (2024-07-29 07:29:47 +0200)

----------------------------------------------------------------
QAPI patches patches for 2024-07-29

----------------------------------------------------------------
Markus Armbruster (1):
      qapi/machine: Belatedly document target loongarch64 is since 7.1

Stefano Garzarella (1):
      qapi/qom: make some QOM properties depend on the build settings

 qapi/crypto.json  |  3 ++-
 qapi/machine.json |  2 ++
 qapi/qom.json     | 21 ++++++++++++++-------
 3 files changed, 18 insertions(+), 8 deletions(-)

-- 
2.45.0



             reply	other threads:[~2024-07-29  6:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-29  6:37 Markus Armbruster [this message]
2024-07-29  6:37 ` [PULL 1/2] qapi/qom: make some QOM properties depend on the build settings Markus Armbruster
2024-07-29  6:37 ` [PULL 2/2] qapi/machine: Belatedly document target loongarch64 is since 7.1 Markus Armbruster
2024-07-30  0:18 ` [PULL 0/2] QAPI patches patches for 2024-07-29 Richard Henderson

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=20240729063722.839708-1-armbru@redhat.com \
    --to=armbru@redhat.com \
    --cc=qemu-devel@nongnu.org \
    --cc=richard.henderson@linaro.org \
    /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).