qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <laurent@vivier.eu>
To: qemu-devel@nongnu.org
Cc: qemu-trivial@nongnu.org, Laurent Vivier <laurent@vivier.eu>
Subject: [PULL 0/6] Trivial branch for 6.2 patches
Date: Mon,  1 Nov 2021 09:27:41 +0100	[thread overview]
Message-ID: <20211101082747.2524909-1-laurent@vivier.eu> (raw)

The following changes since commit af531756d25541a1b3b3d9a14e72e7fedd941a2e:

  Merge remote-tracking branch 'remotes/philmd/tags/renesas-20211030' into staging (2021-10-30 11:31:41 -0700)

are available in the Git repository at:

  git://github.com/vivier/qemu.git tags/trivial-branch-for-6.2-pull-request

for you to fetch changes up to c3f93230df9ad1d3260f03655faa8f9f23c90a52:

  hw/input/lasips2: QOM'ify the Lasi PS/2 (2021-10-31 21:05:40 +0100)

----------------------------------------------------------------
Trivial patches branch pull request 20211101

----------------------------------------------------------------

Markus Armbruster (1):
  monitor: Trim some trailing space from human-readable output

Philippe Mathieu-Daudé (4):
  MAINTAINERS: Split HPPA TCG vs HPPA machines/hardware
  hw/input/lasips2: Fix typos in function names
  hw/input/lasips2: Move LASIPS2State declaration to
    'hw/input/lasips2.h'
  hw/input/lasips2: QOM'ify the Lasi PS/2

Yanan Wang (1):
  hw/core/machine: Add the missing delimiter in cpu_slot_to_string()

 MAINTAINERS                |  5 ++-
 hw/core/machine.c          |  3 ++
 hw/hppa/lasi.c             | 10 +++++-
 hw/input/lasips2.c         | 64 +++++++++++++++++++-------------------
 include/hw/input/lasips2.h | 31 ++++++++++++++++--
 monitor/hmp-cmds.c         |  2 +-
 target/i386/cpu-dump.c     |  4 +--
 target/i386/cpu.c          |  2 +-
 target/ppc/cpu_init.c      |  2 +-
 target/s390x/cpu_models.c  |  4 +--
 target/xtensa/mmu_helper.c |  2 +-
 11 files changed, 83 insertions(+), 46 deletions(-)

-- 
2.31.1



             reply	other threads:[~2021-11-01  8:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-01  8:27 Laurent Vivier [this message]
2021-11-01  8:27 ` [PULL 1/6] monitor: Trim some trailing space from human-readable output Laurent Vivier
2021-11-01  8:27 ` [PULL 2/6] hw/core/machine: Add the missing delimiter in cpu_slot_to_string() Laurent Vivier
2021-11-01  8:27 ` [PULL 3/6] MAINTAINERS: Split HPPA TCG vs HPPA machines/hardware Laurent Vivier
2021-11-01  8:27 ` [PULL 4/6] hw/input/lasips2: Fix typos in function names Laurent Vivier
2021-11-01  8:27 ` [PULL 5/6] hw/input/lasips2: Move LASIPS2State declaration to 'hw/input/lasips2.h' Laurent Vivier
2021-11-01  8:27 ` [PULL 6/6] hw/input/lasips2: QOM'ify the Lasi PS/2 Laurent Vivier
2021-11-01 15:31   ` Richard Henderson
2021-11-01 15:43     ` Philippe Mathieu-Daudé
2021-11-02 16:48       ` Philippe Mathieu-Daudé
  -- strict thread matches above, loose matches on Subject: below --
2021-11-09  9:12 [PULL 0/6] Trivial branch for 6.2 patches Laurent Vivier
2021-11-09 12:14 ` 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=20211101082747.2524909-1-laurent@vivier.eu \
    --to=laurent@vivier.eu \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-trivial@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).