From: Peter Maydell <peter.maydell@linaro.org>
To: Laurent Vivier <laurent@vivier.eu>
Cc: QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [PULL 0/5] M68k for 6.0 patches
Date: Sat, 12 Dec 2020 19:53:59 +0000 [thread overview]
Message-ID: <CAFEAcA9h4tsHeJkvEG9DCmt5pOLhBfMQ8UBsKYerMyseGbjV3g@mail.gmail.com> (raw)
In-Reply-To: <20201212175458.259960-1-laurent@vivier.eu>
On Sat, 12 Dec 2020 at 18:32, Laurent Vivier <laurent@vivier.eu> wrote:
>
> The following changes since commit ad717e6da3852b5729217d7938eecdb81c546114:
>
> Merge remote-tracking branch 'remotes/kevin/tags/for-upstream' into staging=
> (2020-12-12 00:20:46 +0000)
>
> are available in the Git repository at:
>
> git://github.com/vivier/qemu-m68k.git tags/m68k-for-6.0-pull-request
>
> for you to fetch changes up to ce00ff729ee8461dc94a1593d25ceda65d973d3c:
>
> m68k: fix some comment spelling errors (2020-12-12 18:12:43 +0100)
>
> ----------------------------------------------------------------
> m68k pull request 20201212
>
> Fix for Coverity CID 1421883
> Fix some comment spelling errors
> Add m68k vmstate
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/6.0
for any user-visible changes.
-- PMM
next prev parent reply other threads:[~2020-12-12 21:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-12 17:54 [PULL 0/5] M68k for 6.0 patches Laurent Vivier
2020-12-12 17:54 ` [PULL 1/5] hw/m68k/q800: Don't connect two qemu_irqs directly to the same input Laurent Vivier
2020-12-12 17:54 ` [PULL 2/5] hw/m68k/q800.c: Make the GLUE chip an actual QOM device Laurent Vivier
2020-12-12 17:54 ` [PULL 3/5] target/m68k: remove useless qregs array Laurent Vivier
2020-12-12 17:54 ` [PULL 4/5] target/m68k: Add vmstate definition for M68kCPU Laurent Vivier
2020-12-12 17:54 ` [PULL 5/5] m68k: fix some comment spelling errors Laurent Vivier
2020-12-12 19:53 ` Peter Maydell [this message]
2021-03-15 20:42 [PULL 0/5] M68k for 6.0 patches Laurent Vivier
2021-03-17 13:34 ` 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=CAFEAcA9h4tsHeJkvEG9DCmt5pOLhBfMQ8UBsKYerMyseGbjV3g@mail.gmail.com \
--to=peter.maydell@linaro.org \
--cc=laurent@vivier.eu \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.