From: Peter Maydell <peter.maydell@linaro.org>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PULL 0/4] qemu-sparc queue 20210106
Date: Wed, 6 Jan 2021 15:51:42 +0000 [thread overview]
Message-ID: <CAFEAcA8-DUxoZY6WC+XDrDLTRYn8o9L+uV3qXm0sVV23CrePPg@mail.gmail.com> (raw)
In-Reply-To: <20210106120526.29857-1-mark.cave-ayland@ilande.co.uk>
On Wed, 6 Jan 2021 at 12:05, Mark Cave-Ayland
<mark.cave-ayland@ilande.co.uk> wrote:
>
> The following changes since commit 2e0b5bbe813930021b2baab03c9d424c1c52d18b:
>
> Merge remote-tracking branch 'remotes/philmd-gitlab/tags/mips-20210104' into staging (2021-01-05 21:06:42 +0000)
>
> are available in the Git repository at:
>
> git://github.com/mcayland/qemu.git tags/qemu-sparc-20210106
>
> for you to fetch changes up to a879306ca14de576d3a5dd51f830ebf89753e223:
>
> sun4m: don't connect two qemu_irqs directly to the same input (2021-01-06 11:41:37 +0000)
>
> ----------------------------------------------------------------
> qemu-sparc queue
>
> ----------------------------------------------------------------
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/6.0
for any user-visible changes.
-- PMM
prev parent reply other threads:[~2021-01-06 15:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 12:05 [PULL 0/4] qemu-sparc queue 20210106 Mark Cave-Ayland
2021-01-06 12:05 ` [PULL 1/4] hw/timer/slavio_timer: Allow 64-bit accesses Mark Cave-Ayland
2021-01-06 12:05 ` [PULL 2/4] hw/sparc: Make grlib-irqmp device handle its own inbound IRQ lines Mark Cave-Ayland
2021-01-06 12:05 ` [PULL 3/4] include/hw/sparc/grlib.h: Remove unused set_pil_in_fn typedef Mark Cave-Ayland
2021-01-06 12:05 ` [PULL 4/4] sun4m: don't connect two qemu_irqs directly to the same input Mark Cave-Ayland
2021-01-06 15:51 ` Peter Maydell [this message]
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=CAFEAcA8-DUxoZY6WC+XDrDLTRYn8o9L+uV3qXm0sVV23CrePPg@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=mark.cave-ayland@ilande.co.uk \
--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).