From: David Hildenbrand <david@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Michael S. Tsirkin" <mst@redhat.com>, Gavin Shan <gshan@redhat.com>
Subject: Re: [PATCH v1] virtio-mem: Simplify bitmap handling and virtio_mem_set_block_state()
Date: Fri, 23 Jun 2023 14:51:11 +0200 [thread overview]
Message-ID: <39b97e00-fb3c-29b2-aa1f-1de4c8094899@redhat.com> (raw)
In-Reply-To: <20230523183036.517957-1-david@redhat.com>
On 23.05.23 20:30, David Hildenbrand wrote:
> Let's separate plug and unplug handling to prepare for future changes
> and make the code a bit easier to read -- working on block states
> (plugged/unplugged) instead of on a bitmap.
>
> Cc: "Michael S. Tsirkin" <mst@redhat.com>
> Cc: Gavin Shan <gshan@redhat.com>
> Signed-off-by: David Hildenbrand <david@redhat.com>
> ---
I queued this to
https://github.com/davidhildenbrand/qemu.git mem-next
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2023-06-23 12:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-23 18:30 [PATCH v1] virtio-mem: Simplify bitmap handling and virtio_mem_set_block_state() David Hildenbrand
2023-06-23 12:51 ` David Hildenbrand [this message]
2023-06-25 21:06 ` Michael S. Tsirkin
2023-06-26 7:45 ` David Hildenbrand
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=39b97e00-fb3c-29b2-aa1f-1de4c8094899@redhat.com \
--to=david@redhat.com \
--cc=gshan@redhat.com \
--cc=mst@redhat.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).