From: Richard Henderson <richard.henderson@linaro.org>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>, qemu-devel@nongnu.org
Subject: Re: [PULL 0/2] qemu-sparc queue 20211121
Date: Sun, 21 Nov 2021 16:47:43 +0100 [thread overview]
Message-ID: <2a3d4701-ba69-9e9d-2246-4cccec2c1d64@linaro.org> (raw)
In-Reply-To: <20211121095933.28174-1-mark.cave-ayland@ilande.co.uk>
On 11/21/21 10:59 AM, Mark Cave-Ayland wrote:
> The following changes since commit 8627edfb3f1fca24a96a0954148885c3241c10f8:
>
> Merge tag 'for-upstream' of https://gitlab.com/bonzini/qemu into staging (2021-11-19 17:16:57 +0100)
>
> are available in the Git repository at:
>
> git://github.com/mcayland/qemu.git tags/qemu-sparc-20211121
>
> for you to fetch changes up to 319e89cdc32096432b578152a47d0d156033b711:
>
> escc: update the R_SPEC register SPEC_ALLSENT bit when writing to W_TXCTRL1 (2021-11-21 09:56:52 +0000)
>
> ----------------------------------------------------------------
> qemu-sparc queue
> - contains fixes for ESCC reset issues with Sun PROM and OpenBSD on SPARC32
>
> ----------------------------------------------------------------
> Mark Cave-Ayland (2):
> escc: always set STATUS_TXEMPTY in R_STATUS on device reset
> escc: update the R_SPEC register SPEC_ALLSENT bit when writing to W_TXCTRL1
>
> hw/char/escc.c | 25 +++++++++++++++++++++++++
> 1 file changed, 25 insertions(+)
Applied, thanks.
r~
prev parent reply other threads:[~2021-11-21 15:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-21 9:59 [PULL 0/2] qemu-sparc queue 20211121 Mark Cave-Ayland
2021-11-21 9:59 ` [PULL 1/2] escc: always set STATUS_TXEMPTY in R_STATUS on device reset Mark Cave-Ayland
2021-11-21 9:59 ` [PULL 2/2] escc: update the R_SPEC register SPEC_ALLSENT bit when writing to W_TXCTRL1 Mark Cave-Ayland
2021-11-21 15:47 ` Richard Henderson [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=2a3d4701-ba69-9e9d-2246-4cccec2c1d64@linaro.org \
--to=richard.henderson@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).