From: Stefan Hajnoczi <stefanha@gmail.com>
To: n.alekseev2104@gmail.com
Cc: qemu-devel@nongnu.org, jusual@mail.ru, kwolf@redhat.com,
mreitz@redhat.com
Subject: Re: [Qemu-devel] [PATCH] Add coroutine_fn to bdrv_check_co_entry
Date: Wed, 3 Apr 2019 13:05:31 +0100 [thread overview]
Message-ID: <20190403120531.GC32425@stefanha-x1.localdomain> (raw)
In-Reply-To: <20190401093051.16488-1-n.alekseev2104@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 769 bytes --]
On Mon, Apr 01, 2019 at 12:30:51PM +0300, n.alekseev2104@gmail.com wrote:
> From: Nikita Alekseev <n.alekseev2104@gmail.com>
>
> bdrv_check_co_entry calls bdrv_co_check, which is a coroutine function.
> Thus, it also needs to be marked as a coroutine.
>
> Signed-off-by: Nikita Alekseev <n.alekseev2104@gmail.com>
> ---
> block.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
Thank you! I prefixed the commit message with "block: ". Most commits
have a subsystem prefix to make browsing/searching git log easier. In
the future you can add it yourself - look at git log for a file to
discover what prefix other people recently used.
Thanks, applied to my block-next tree:
https://github.com/stefanha/qemu/commits/block-next
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2019-04-03 12:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 9:30 [Qemu-devel] [PATCH] Add coroutine_fn to bdrv_check_co_entry n.alekseev2104
2019-04-03 12:05 ` Stefan Hajnoczi [this message]
[not found] <20190331083917.32176-1-n.alekseev2104@gmail.com>
2019-04-01 9:15 ` Stefan Hajnoczi
2019-04-01 11:31 ` Nikita
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=20190403120531.GC32425@stefanha-x1.localdomain \
--to=stefanha@gmail.com \
--cc=jusual@mail.ru \
--cc=kwolf@redhat.com \
--cc=mreitz@redhat.com \
--cc=n.alekseev2104@gmail.com \
--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).