qemu-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v3] tests/acceptance: test hot(un)plug of ccw devices


From: Philippe Mathieu-Daudé
Subject: Re: [PATCH v3] tests/acceptance: test hot(un)plug of ccw devices
Date: Wed, 9 Dec 2020 19:27:30 +0100
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.5.0

On 12/9/20 7:22 PM, Cornelia Huck wrote:
> On Wed, 9 Dec 2020 19:09:25 +0100
> Philippe Mathieu-Daudé <philmd@redhat.com> wrote:
> 
>> Hi Paolo, Fam,
>>
>> On 12/8/20 1:28 PM, Cornelia Huck wrote:
>>> Hotplug a virtio-net-ccw device, and then hotunplug it again.
>>>
>>> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
>>> ---
>>> v2->v3:
>>> - do the dmesg cleanout and waiting for messages properly [Thomas]
>>>
>>> Wainer: I dropped your r-b, as there had been too many changes for
>>>         me to be comfortable with retaining it
>>>
>>> ---
>>>  tests/acceptance/machine_s390_ccw_virtio.py | 24 +++++++++++++++++++++
>>>  1 file changed, 24 insertions(+)  
>>
>> Patchew failed applying this patch... Any idea what got wrong?
>>
>> Switched to a new branch '20201208122843.147186-1-cohuck@redhat.com'
>> Applying: tests/acceptance: test hot(un)plug of ccw devices
>> error: sha1 information is lacking or useless
>> (tests/acceptance/machine_s390_ccw_virtio.py).
>> error: could not build fake ancestor
>> hint: Use 'git am --show-current-patch=diff' to see the failed patch
>> Patch failed at 0001 tests/acceptance: test hot(un)plug of ccw devices
>> When you have resolved this problem, run "git am --continue".
>> If you prefer to skip this patch, run "git am --skip" instead.
>> To restore the original branch and stop patching, run "git am --abort".
>> Failed to apply patch:
>> [PATCH v3] tests/acceptance: test hot(un)plug of ccw devices
>>
>> 20201208122843.147186-1-cohuck@redhat.com/">https://patchew.org/QEMU/20201208122843.147186-1-cohuck@redhat.com/
>>
> 
> Hm, seems I forgot to include the base version, which should be my
> current s390-next branch...

Ah OK, we are good then, thanks!

Phil.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]