From: "Philippe Mathieu-Daudé" <philmd@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Kevin Wolf" <kwolf@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@redhat.com>,
qemu-block@nongnu.org, "Max Reitz" <mreitz@redhat.com>
Subject: [Qemu-devel] [PULL 0/2] pflash-next patches for v4.1.0-rc1
Date: Tue, 16 Jul 2019 18:01:41 +0200 [thread overview]
Message-ID: <20190716160143.394-1-philmd@redhat.com> (raw)
The following changes since commit 697f59243f5a28b8a243ff5ad59e34bbecffcae1:
Merge remote-tracking branch 'remotes/bonzini/tags/for-upstream' into staging (2019-07-16 15:08:29 +0100)
are available in the Git repository at:
https://gitlab.com/philmd/qemu.git tags/pflash-next-20190716
for you to fetch changes up to 611c749c3b86fe377c94ea301feab3d9ce3bf617:
hw/block/pflash_cfi01: Start state machine as READY to accept commands (2019-07-16 17:54:06 +0200)
----------------------------------------------------------------
Trivial pflash fixes for rc1.
----------------------------------------------------------------
Philippe Mathieu-Daudé (2):
hw/block/pflash_cfi02: Explicit switch fallthrough for ERASE commands
hw/block/pflash_cfi01: Start state machine as READY to accept commands
hw/block/pflash_cfi01.c | 2 +-
hw/block/pflash_cfi02.c | 1 +
2 files changed, 2 insertions(+), 1 deletion(-)
--
2.20.1
next reply other threads:[~2019-07-16 16:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-16 16:01 Philippe Mathieu-Daudé [this message]
2019-07-16 16:01 ` [Qemu-devel] [PULL 1/2] hw/block/pflash_cfi02: Explicit switch fallthrough for ERASE commands Philippe Mathieu-Daudé
2019-07-16 16:01 ` [Qemu-devel] [PULL 2/2] hw/block/pflash_cfi01: Start state machine as READY to accept commands Philippe Mathieu-Daudé
2019-07-16 16:30 ` [Qemu-devel] [PULL 0/2] pflash-next patches for v4.1.0-rc1 Peter Maydell
2019-07-16 21:32 ` no-reply
2019-07-16 22:02 ` Philippe Mathieu-Daudé
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=20190716160143.394-1-philmd@redhat.com \
--to=philmd@redhat.com \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=qemu-block@nongnu.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).