qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Richard Henderson <richard.henderson@linaro.org>
To: Stefan Hajnoczi <stefanha@redhat.com>, qemu-devel@nongnu.org
Cc: Julia Suvorova <jusual@redhat.com>,
	qemu-block@nongnu.org, Stefano Garzarella <sgarzare@redhat.com>,
	Hanna Reitz <hreitz@redhat.com>, Kevin Wolf <kwolf@redhat.com>,
	Aarushi Mehta <mehta.aaru20@gmail.com>
Subject: Re: [PULL 0/2] Block patches
Date: Thu, 7 Jul 2022 16:21:22 +0530	[thread overview]
Message-ID: <5e412493-5892-59c8-b4f1-a5ea7d2ec3f8@linaro.org> (raw)
In-Reply-To: <20220707081247.1416955-1-stefanha@redhat.com>

On 7/7/22 13:42, Stefan Hajnoczi wrote:
> The following changes since commit 8e9398e3b1a860b8c29c670c1b6c36afe8d87849:
> 
>    Merge tag 'pull-ppc-20220706' of https://gitlab.com/danielhb/qemu into staging (2022-07-07 06:21:05 +0530)
> 
> are available in the Git repository at:
> 
>    https://gitlab.com/stefanha/qemu.git tags/block-pull-request
> 
> for you to fetch changes up to be6a166fde652589761cf70471bcde623e9bd72a:
> 
>    block/io_uring: clarify that short reads can happen (2022-07-07 09:04:15 +0100)
> 
> ----------------------------------------------------------------
> Pull request

Applied, thanks.  Please update https://wiki.qemu.org/ChangeLog/7.1 as appropriate.


r~


> 
> ----------------------------------------------------------------
> 
> Dominique Martinet (1):
>    io_uring: fix short read slow path
> 
> Stefan Hajnoczi (1):
>    block/io_uring: clarify that short reads can happen
> 
>   block/io_uring.c | 12 ++++--------
>   1 file changed, 4 insertions(+), 8 deletions(-)
> 



  parent reply	other threads:[~2022-07-07 10:54 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07  8:12 [PULL 0/2] Block patches Stefan Hajnoczi
2022-07-07  8:12 ` [PULL 1/2] io_uring: fix short read slow path Stefan Hajnoczi
2022-07-07  8:12 ` [PULL 2/2] block/io_uring: clarify that short reads can happen Stefan Hajnoczi
2022-07-07 10:51 ` Richard Henderson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-01-22 16:01 [PULL 0/2] Block patches Stefan Hajnoczi
2024-01-25 15:11 ` Peter Maydell
2024-01-25 15:47 ` Michael Tokarev
2023-04-24 17:55 Stefan Hajnoczi
2023-04-25 11:15 ` Richard Henderson
2021-10-11 12:40 Stefan Hajnoczi
2021-10-11 18:23 ` Richard Henderson
2021-03-24 14:52 Stefan Hajnoczi
2021-03-24 18:05 ` Peter Maydell
2021-03-24 20:18   ` Vladimir Sementsov-Ogievskiy
2021-03-24 20:42     ` Peter Maydell
2021-03-25  9:56       ` Stefan Hajnoczi
2021-03-25 10:17         ` Vladimir Sementsov-Ogievskiy
2021-03-25 16:28           ` Stefan Hajnoczi
2021-03-25 16:36             ` Peter Maydell
2021-03-25 17:40               ` Stefan Hajnoczi
2021-03-26 10:22 ` Peter Maydell
2020-02-10  9:23 Stefan Hajnoczi
2020-02-10 18:09 ` Peter Maydell
2019-12-13 14:33 Stefan Hajnoczi
2019-12-13 21:10 ` Peter Maydell
2019-10-25 19:18 Stefan Hajnoczi
2019-10-26  9:13 ` Peter Maydell
2019-09-25 17:43 Stefan Hajnoczi
2019-09-26  6:16 ` no-reply
2019-09-26 12:06   ` Vladimir Sementsov-Ogievskiy
2019-09-26 12:56 ` 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=5e412493-5892-59c8-b4f1-a5ea7d2ec3f8@linaro.org \
    --to=richard.henderson@linaro.org \
    --cc=hreitz@redhat.com \
    --cc=jusual@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mehta.aaru20@gmail.com \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=sgarzare@redhat.com \
    --cc=stefanha@redhat.com \
    /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).