From: Kevin Wolf <kwolf@redhat.com>
To: Fabiano Rosas <farosas@suse.de>
Cc: qemu-devel@nongnu.org, qemu-block@nongnu.org
Subject: Re: [PATCH RESEND 0/2] block/qapi: Dead code cleanup
Date: Mon, 4 Sep 2023 11:04:11 +0200 [thread overview]
Message-ID: <ZPWdi5NYEpxPHdt9@redhat.com> (raw)
In-Reply-To: <20230901184605.32260-1-farosas@suse.de>
Am 01.09.2023 um 20:46 hat Fabiano Rosas geschrieben:
> Hi,
>
> I'm resending a couple of already reviewed patches that were part of a
> larger series[1].
>
> Thanks
>
> 1- https://lore.kernel.org/r/20230609201910.12100-1-farosas@suse.de
>
> Fabiano Rosas (2):
> block: Remove bdrv_query_block_node_info
> block: Remove unnecessary variable in bdrv_block_device_info
Thanks, applied to the block branch.
Kevin
prev parent reply other threads:[~2023-09-04 9:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-01 18:46 [PATCH RESEND 0/2] block/qapi: Dead code cleanup Fabiano Rosas
2023-09-01 18:46 ` [PATCH RESEND 1/2] block: Remove bdrv_query_block_node_info Fabiano Rosas
2023-09-01 18:46 ` [PATCH RESEND 2/2] block: Remove unnecessary variable in bdrv_block_device_info Fabiano Rosas
2023-09-04 9:04 ` Kevin Wolf [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=ZPWdi5NYEpxPHdt9@redhat.com \
--to=kwolf@redhat.com \
--cc=farosas@suse.de \
--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).