qemu-devel
[Top][All Lists]
Advanced

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

Re: [Qemu-devel] [PULL v2 00/28] Kconfig for Arm machines


From: Thomas Huth
Subject: Re: [Qemu-devel] [PULL v2 00/28] Kconfig for Arm machines
Date: Thu, 9 May 2019 07:34:09 +0200
User-agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1

On 08/05/2019 18.45, Philippe Mathieu-Daudé wrote:
> [clicked ctrl+enter too fast]
> 
> On Wed, May 8, 2019 at 6:43 PM Philippe Mathieu-Daudé <address@hidden> wrote:
>> On 5/8/19 5:33 PM, Thomas Huth wrote:
>>> On 08/05/2019 17.09, Peter Maydell wrote:
>>>> On Tue, 7 May 2019 at 14:45, Thomas Huth <address@hidden> wrote:
>>>>>
>>>>>  Hi Peter,
>>>>>
>>>>> the following changes since commit 
>>>>> a6ae23831b05a11880b40f7d58e332c45a6b04f7:
>>>>>
>>>>>   Merge remote-tracking branch 
>>>>> 'remotes/ehabkost/tags/python-next-pull-request' into staging (2019-05-03 
>>>>> 15:26:09 +0100)
>>>>>
>>>>> are available in the Git repository at:
>>>>>
>>>>>   https://gitlab.com/huth/qemu.git tags/pull-request-2019-05-07
>>>>>
>>>>> for you to fetch changes up to 69f879e9fefab9aaf24893fe4ce23e07756d703c:
>>>>>
>>>>>   hw/arm: Remove hard-enablement of the remaining PCI devices (2019-05-07 
>>>>> 15:01:47 +0200)
>>>>>
>>>>> ----------------------------------------------------------------
>>>>> Kconfig settings for the Arm machines
>>>>> (v2: Fix the dependency of q35 to AHCI_ICH9 in the second patch)
>>>>> ----------------------------------------------------------------
>>>>
>>>> Hi -- this is still failing in the build test where I 'make clean'
>>>
>>> Very weird. What is running before the "make clean"? Could you provide
>>> me with the content of i386-softmmu/config-devices.mak please?
>>
>> It worked for me after running 'git fetch --tags', maybe because Thomas
>> used the same tag?
> 
> Maybe because Thomas used the same tag you are still trying the
> previous version?

I did not use the same tag. v1 had pull-request-2019-05-05 while v2 has
pull-request-2019-05-07. So this can not be the reason.

 Thomas





reply via email to

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