From: Paolo Bonzini <pbonzini@redhat.com>
To: Kevin Wolf <kwolf@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"open list:Block layer core" <qemu-block@nongnu.org>
Subject: Re: [PATCH] block: split qemu/aio.h out of block/aio.h
Date: Tue, 2 Dec 2025 17:09:04 +0100 [thread overview]
Message-ID: <CABgObfYb6-7QGObFBWWdQBzMtLhmuFNkidq4JYe2wgmiS81zjw@mail.gmail.com> (raw)
In-Reply-To: <aS8N4_LDyW1DrF_x@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 511 bytes --]
Il mar 2 dic 2025, 17:03 Kevin Wolf <kwolf@redhat.com> ha scritto:
> Is it really worth keeping a separate tiny include file for BlockAIOCB?
> Maybe let's have a patch to move it and its three functions to
> block-common.h, and then just move this file unchanged into the place
> where it should always have been.
>
Ok, sure! I did it this way just because it avoided the full-tree change to
rename the include file, but I will reorganize it as a content
reorganization + rename instead.
Paolo
> Kevin
>
>
[-- Attachment #2: Type: text/html, Size: 1177 bytes --]
prev parent reply other threads:[~2025-12-02 16:11 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
2025-12-02 16:03 ` Kevin Wolf
2025-12-02 16:09 ` Paolo Bonzini [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=CABgObfYb6-7QGObFBWWdQBzMtLhmuFNkidq4JYe2wgmiS81zjw@mail.gmail.com \
--to=pbonzini@redhat.com \
--cc=kwolf@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).