From: Markus Armbruster <armbru@redhat.com>
To: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Cc: qemu-devel@nongnu.org, atar4qemu@gmail.com,
"Jakub Jermář" <jakub@jermar.eu>,
qemu-stable@nongnu.org
Subject: Re: [PATCH] Revert "hw/sparc64/niagara: Use blk_name() instead of open-coding it"
Date: Tue, 16 May 2023 10:04:20 +0200 [thread overview]
Message-ID: <87ilcsvh17.fsf@pond.sub.org> (raw)
In-Reply-To: <3334226e-f96e-5f17-2b67-f29bb9f0256a@ilande.co.uk> (Mark Cave-Ayland's message of "Tue, 16 May 2023 08:00:29 +0100")
Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk> writes:
> On 15/05/2023 16:11, Markus Armbruster wrote:
>
>> This reverts commit 1881f336a33a8a99cb17ab1c57ed953682e8e107.
>> This commit breaks "-drive if=pflash,readonly=on,file=image.iso". It
>> claims to merely replace an open-coded version of blk_name() by a
>> call, but that's not the case. Sorry for the inconvenience!
>
> Ah so was this a case of replacing something that shouldn't have been replaced in the first place, or does it require a follow-up patch?
I was looking at inclusions of block/block_int*.h outside the block
subsystem, and went "Oh, I can get rid of this one!" Nope, brain
malfunction.
Reducing such inclusions is always nice, but the code this patch
restores isn't broken, and no follow-up fix is required.
>> Reported-by: Jakub Jermář <jakub@jermar.eu>
>> Cc: qemu-stable@nongnu.org
>> Signed-off-by: Markus Armbruster <armbru@redhat.com>
[...]
> Regardless of the above:
>
> Acked-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
Thanks!
next prev parent reply other threads:[~2023-05-16 8:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-15 15:11 [PATCH] Revert "hw/sparc64/niagara: Use blk_name() instead of open-coding it" Markus Armbruster
2023-05-16 7:00 ` Mark Cave-Ayland
2023-05-16 8:04 ` Markus Armbruster [this message]
2023-05-16 15:08 ` Philippe Mathieu-Daudé
2023-06-27 6:48 ` Mark Cave-Ayland
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=87ilcsvh17.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=atar4qemu@gmail.com \
--cc=jakub@jermar.eu \
--cc=mark.cave-ayland@ilande.co.uk \
--cc=qemu-devel@nongnu.org \
--cc=qemu-stable@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).