From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Markus Armbruster <armbru@redhat.com>, qemu-devel@nongnu.org
Cc: 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 08:00:29 +0100 [thread overview]
Message-ID: <3334226e-f96e-5f17-2b67-f29bb9f0256a@ilande.co.uk> (raw)
In-Reply-To: <20230515151104.1350155-1-armbru@redhat.com>
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?
> Reported-by: Jakub Jermář <jakub@jermar.eu>
> Cc: qemu-stable@nongnu.org
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
> hw/sparc64/niagara.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/hw/sparc64/niagara.c b/hw/sparc64/niagara.c
> index 6725cc61fd..ab3c4ec346 100644
> --- a/hw/sparc64/niagara.c
> +++ b/hw/sparc64/niagara.c
> @@ -23,6 +23,7 @@
> */
>
> #include "qemu/osdep.h"
> +#include "block/block_int-common.h"
> #include "qemu/units.h"
> #include "cpu.h"
> #include "hw/boards.h"
> @@ -143,9 +144,10 @@ static void niagara_init(MachineState *machine)
> memory_region_add_subregion(get_system_memory(),
> NIAGARA_VDISK_BASE, &s->vdisk_ram);
> dinfo->is_default = 1;
> - rom_add_file_fixed(blk_name(blk), NIAGARA_VDISK_BASE, -1);
> + rom_add_file_fixed(blk_bs(blk)->filename, NIAGARA_VDISK_BASE, -1);
> } else {
> - error_report("could not load ram disk '%s'", blk_name(blk));
> + error_report("could not load ram disk '%s'",
> + blk_bs(blk)->filename);
> exit(1);
> }
> }
Regardless of the above:
Acked-by: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
ATB,
Mark.
next prev parent reply other threads:[~2023-05-16 7:01 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 [this message]
2023-05-16 8:04 ` Markus Armbruster
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=3334226e-f96e-5f17-2b67-f29bb9f0256a@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--cc=armbru@redhat.com \
--cc=atar4qemu@gmail.com \
--cc=jakub@jermar.eu \
--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).