From: Peter Maydell <peter.maydell@linaro.org>
To: Max Reitz <mreitz@redhat.com>
Cc: Kevin Wolf <kwolf@redhat.com>,
QEMU Developers <qemu-devel@nongnu.org>,
Qemu-block <qemu-block@nongnu.org>
Subject: Re: [Qemu-devel] [PULL 0/1] Block patches for 4.1.0-rc3
Date: Tue, 30 Jul 2019 17:00:00 +0100 [thread overview]
Message-ID: <CAFEAcA8US1DPidO1XArsBB50qD=SQkDH4u7euiD97Vrb2wJN1g@mail.gmail.com> (raw)
In-Reply-To: <20190730125910.32060-1-mreitz@redhat.com>
On Tue, 30 Jul 2019 at 13:59, Max Reitz <mreitz@redhat.com> wrote:
>
> The following changes since commit 6e9a6cbe7d56107f5e0d7711905dc19bb4d7e3f0:
>
> Merge remote-tracking branch 'remotes/kevin/tags/for-upstream' into staging (2019-07-30 12:25:35 +0100)
>
> are available in the Git repository at:
>
> https://github.com/XanClic/qemu.git tags/pull-block-2019-07-30
>
> for you to fetch changes up to 1120407bdf70a2c4681464ae08bdb7c615566200:
>
> nvme: Limit blkshift to 12 (for 4 kB blocks) (2019-07-30 14:49:24 +0200)
>
> ----------------------------------------------------------------
> Block patch for 4.1.0-rc3:
> - Fix CID 1403771 in block/nvme.c
>
> ----------------------------------------------------------------
> Max Reitz (1):
> nvme: Limit blkshift to 12 (for 4 kB blocks)
>
> block/nvme.c | 22 +++++++++++-----------
> 1 file changed, 11 insertions(+), 11 deletions(-)
>
Applied, thanks.
Please update the changelog at https://wiki.qemu.org/ChangeLog/4.1
for any user-visible changes.
-- PMM
prev parent reply other threads:[~2019-07-30 16:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-30 12:59 [Qemu-devel] [PULL 0/1] Block patches for 4.1.0-rc3 Max Reitz
2019-07-30 12:59 ` [Qemu-devel] [PULL 1/1] nvme: Limit blkshift to 12 (for 4 kB blocks) Max Reitz
2019-07-30 16:00 ` 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='CAFEAcA8US1DPidO1XArsBB50qD=SQkDH4u7euiD97Vrb2wJN1g@mail.gmail.com' \
--to=peter.maydell@linaro.org \
--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).