From: Mark Cave-Ayland <mark.cave-ayland@ilande.co.uk>
To: Thomas Huth <thuth@redhat.com>,
armbru@redhat.com, david@gibson.dropbear.id.au,
atar4qemu@gmail.com, qemu-devel@nongnu.org, qemu-ppc@nongnu.org
Subject: Re: [PATCH v2 5/6] macio: don't reference serial_hd() directly within the device
Date: Tue, 10 Nov 2020 09:03:44 +0000 [thread overview]
Message-ID: <74b3fd72-01ce-c071-4f12-7037fd93a25e@ilande.co.uk> (raw)
In-Reply-To: <53c02ed9-c21a-a628-753c-09f3f4e632f4@redhat.com>
On 09/11/2020 10:02, Thomas Huth wrote:
>>>> Just out of interest how did you find this? My new workflow involves a local
>>>> "make check" with all ppc targets and a pass through Travis-CI and it didn't
>>>> show up there for me (or indeed Peter's pre-merge tests).
>>>
>>> I've found it with the scripts/device-crash-test script. (You currently need
>>> to apply Eduardo's patch "Check if path is actually an executable file" on
>>> top first to run it)
>>
>> Have you got a link for this? I've tried doing some basic searches in my
>> email client and couldn't easily spot it...
>
> https://lists.gnu.org/archive/html/qemu-devel/2020-10/msg07549.html
Thanks for this - I gave it a quick run with my patch and I see that there are still
quite a few failures for qemu-system-ppc, so certainly there are other devices that
will need attention in future.
I've just realised that I didn't explicitly mark the patch as for-5.2 so I'll resend
it along with your R-B tag.
ATB,
Mark.
next prev parent reply other threads:[~2020-11-10 9:05 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-26 14:02 [PATCH v2 0/6] QOM minor fixes Mark Cave-Ayland
2020-09-26 14:02 ` [PATCH v2 1/6] sparc32-dma: use object_initialize_child() for espdma and ledma child objects Mark Cave-Ayland
2020-09-26 14:02 ` [PATCH v2 2/6] sparc32-ledma: use object_initialize_child() for lance child object Mark Cave-Ayland
2020-09-26 14:02 ` [PATCH v2 3/6] sparc32-espdma: use object_initialize_child() for esp " Mark Cave-Ayland
2020-09-26 14:02 ` [PATCH v2 4/6] sparc32-ledma: don't reference nd_table directly within the device Mark Cave-Ayland
2020-09-26 20:11 ` Philippe Mathieu-Daudé
2020-09-26 14:02 ` [PATCH v2 5/6] macio: don't reference serial_hd() " Mark Cave-Ayland
2020-11-04 12:47 ` Thomas Huth
2020-11-04 14:16 ` BALATON Zoltan via
2020-11-04 14:24 ` BALATON Zoltan via
2020-11-04 14:51 ` Thomas Huth
2020-11-05 6:29 ` Markus Armbruster
2020-11-04 19:29 ` Mark Cave-Ayland
2020-11-05 5:31 ` Thomas Huth
2020-11-06 7:35 ` Mark Cave-Ayland
2020-11-09 10:02 ` Thomas Huth
2020-11-10 9:03 ` Mark Cave-Ayland [this message]
2020-09-26 14:02 ` [PATCH v2 6/6] sabre: don't call sysbus_mmio_map() in sabre_realize() Mark Cave-Ayland
2020-10-21 9:18 ` [PATCH v2 0/6] QOM minor fixes 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=74b3fd72-01ce-c071-4f12-7037fd93a25e@ilande.co.uk \
--to=mark.cave-ayland@ilande.co.uk \
--cc=armbru@redhat.com \
--cc=atar4qemu@gmail.com \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=thuth@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.