From: Willian Rampazzo <wrampazz@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: Thomas Huth <thuth@redhat.com>,
qemu-devel <qemu-devel@nongnu.org>,
Wainer dos Santos Moschetta <wainersm@redhat.com>,
Willian Rampazzo <willianr@redhat.com>,
qemu-s390x@nongnu.org, Cleber Rosa <crosa@redhat.com>
Subject: Re: [PATCH v2] tests/acceptance: Add a test with the Fedora 31 kernel and initrd
Date: Mon, 21 Dec 2020 12:10:22 -0300 [thread overview]
Message-ID: <CAKJDGDYW8bhjcyoHrAC_LZ7cfbL7FUBF-2gYmmZnewZ1=aChFg@mail.gmail.com> (raw)
In-Reply-To: <20201221135955.69b0b182.cohuck@redhat.com>
On Mon, Dec 21, 2020 at 10:00 AM Cornelia Huck <cohuck@redhat.com> wrote:
>
> On Fri, 18 Dec 2020 15:23:32 -0300
> Willian Rampazzo <wrampazz@redhat.com> wrote:
>
> > On 12/17/20 5:53 AM, Thomas Huth wrote:
>
> > > + # Hot-plug a virtio-crypto device and see whether it gets accepted
> > > + self.clear_guest_dmesg()
> >
> > Your previous patch "[PATCH 1/3] tests/acceptance: Extract the code to
> > clear dmesg and wait for CRW reports" defined the method as
> > "clear_guests_dmesg". After fixing this in the code:
>
> Hm, I see clear_guest_dmesg in the code I have on my s390-next branch?
Ah, I had his v0 locally
(https://patchew.org/QEMU/20201211173134.376078-1-thuth@redhat.com/20201211173134.376078-2-thuth@redhat.com/).
The v1 is, indeed, clear_guest_dmesg, so, we should be good to go!
prev parent reply other threads:[~2020-12-21 15:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-17 8:53 [PATCH v2] tests/acceptance: Add a test with the Fedora 31 kernel and initrd Thomas Huth
2020-12-18 13:38 ` Cornelia Huck
2020-12-21 13:05 ` Thomas Huth
2020-12-21 13:32 ` Cornelia Huck
2020-12-18 15:05 ` Wainer dos Santos Moschetta
2020-12-21 13:27 ` Thomas Huth
2020-12-18 18:23 ` Willian Rampazzo
2020-12-21 12:59 ` Cornelia Huck
2020-12-21 13:24 ` Thomas Huth
2020-12-21 15:10 ` Willian Rampazzo [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='CAKJDGDYW8bhjcyoHrAC_LZ7cfbL7FUBF-2gYmmZnewZ1=aChFg@mail.gmail.com' \
--to=wrampazz@redhat.com \
--cc=cohuck@redhat.com \
--cc=crosa@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
--cc=willianr@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 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).