qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Markus Armbruster <armbru@redhat.com>
To: qemu-devel@nongnu.org
Cc: peter.maydell@linaro.org
Subject: [PULL 0/9] QAPI patches patches for 2022-02-28
Date: Mon, 28 Feb 2022 12:26:04 +0100	[thread overview]
Message-ID: <20220228112613.520040-1-armbru@redhat.com> (raw)

The following changes since commit fa435db8ce1dff3b15e3f59a12f55f7b3a347b08:

  Merge remote-tracking branch 'remotes/jsnow-gitlab/tags/python-pull-request' into staging (2022-02-24 12:48:14 +0000)

are available in the Git repository at:

  git://repo.or.cz/qemu/armbru.git tags/pull-qapi-2022-02-28

for you to fetch changes up to 1428502c8c0c0cfbb04212558144fef970042cf3:

  qapi: Belatedly adjust limitations documentation (2022-02-28 11:39:35 +0100)

----------------------------------------------------------------
QAPI patches patches for 2022-02-28

----------------------------------------------------------------
Fabian Holler (1):
      qapi/migration: Fix examples document wrong field name for arguments

John Snow (1):
      scripts/qapi: minor delinting

Markus Armbruster (4):
      keyval: Fix grammar comment to cover downstream prefix
      qapi: Fix stale reference to scripts/qapi.py in a comment
      rtc: Have event RTC_CHANGE identify the RTC by QOM path
      qapi: Belatedly adjust limitations documentation

Peter Maydell (3):
      qapi: Move RTC_CHANGE back out of target schema
      qapi: Document some missing details of RTC_CHANGE event
      hw/rtc: Compile pl031 once-only

 qapi/compat.json         |  2 +-
 qapi/migration.json      | 10 +++++-----
 qapi/misc-target.json    | 33 ---------------------------------
 qapi/misc.json           | 26 ++++++++++++++++++++++++++
 hw/ppc/spapr_rtc.c       |  6 ++++--
 hw/rtc/mc146818rtc.c     |  5 +++--
 hw/rtc/pl031.c           |  5 +++--
 qapi/qapi-util.c         |  2 +-
 util/keyval.c            |  4 +++-
 hw/rtc/meson.build       |  2 +-
 scripts/qapi/commands.py |  2 +-
 scripts/qapi/pylintrc    | 16 ++++++----------
 scripts/qapi/types.py    |  6 +++++-
 scripts/qapi/visit.py    |  6 +++++-
 14 files changed, 64 insertions(+), 61 deletions(-)

-- 
2.35.1



             reply	other threads:[~2022-02-28 11:30 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-28 11:26 Markus Armbruster [this message]
2022-02-28 11:26 ` [PULL 1/9] scripts/qapi: minor delinting Markus Armbruster
2022-02-28 11:26 ` [PULL 2/9] keyval: Fix grammar comment to cover downstream prefix Markus Armbruster
2022-02-28 11:26 ` [PULL 3/9] qapi: Fix stale reference to scripts/qapi.py in a comment Markus Armbruster
2022-02-28 11:26 ` [PULL 4/9] qapi/migration: Fix examples document wrong field name for arguments Markus Armbruster
2022-02-28 11:26 ` [PULL 5/9] qapi: Move RTC_CHANGE back out of target schema Markus Armbruster
2022-02-28 11:26 ` [PULL 6/9] qapi: Document some missing details of RTC_CHANGE event Markus Armbruster
2022-02-28 11:26 ` [PULL 7/9] hw/rtc: Compile pl031 once-only Markus Armbruster
2022-02-28 11:26 ` [PULL 8/9] rtc: Have event RTC_CHANGE identify the RTC by QOM path Markus Armbruster
2022-02-28 11:26 ` [PULL 9/9] qapi: Belatedly adjust limitations documentation Markus Armbruster
2022-03-01 13:25 ` [PULL 0/9] QAPI patches patches for 2022-02-28 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=20220228112613.520040-1-armbru@redhat.com \
    --to=armbru@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=qemu-devel@nongnu.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).