From: Paolo Bonzini <pbonzini@redhat.com>
To: Prasad Pandit <ppandit@redhat.com>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [PATCH] block: split qemu/aio.h out of block/aio.h
Date: Tue, 2 Dec 2025 08:42:12 +0100 [thread overview]
Message-ID: <93ab4c50-08d6-4692-82bd-1d01121f7362@redhat.com> (raw)
In-Reply-To: <CAE8KmOwfKfTpE8YOwd6GV0vAetf+rfLW648ALvNWdC0ciL9k8w@mail.gmail.com>
On 11/28/25 14:14, Prasad Pandit wrote:
> Should block/aio.h include qemu/aio.h? User can include them both
> where needed.
block/aio.h is quite useless without functions like aio_co_wake(), so it
includes qemu/aio.h.
Paolo
> Otherwise looks okay.
> Reviewed-by: Prasad Pandit <pjp@fedoraproject.org>
>
> Thank you.
> ---
> - Prasad
>
next prev parent reply other threads:[~2025-12-02 7:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-28 10:15 [PATCH] block: split qemu/aio.h out of block/aio.h Paolo Bonzini
2025-11-28 13:14 ` Prasad Pandit
2025-12-02 7:42 ` Paolo Bonzini [this message]
2025-12-02 16:03 ` Kevin Wolf
2025-12-02 16:09 ` Paolo Bonzini
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=93ab4c50-08d6-4692-82bd-1d01121f7362@redhat.com \
--to=pbonzini@redhat.com \
--cc=ppandit@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).