qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@redhat.com>,
	"Peter Maydell" <peter.maydell@linaro.org>
Cc: qemu-arm <qemu-arm@nongnu.org>, John Snow <jsnow@redhat.com>,
	QEMU Developers <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [PULL v2 00/28] Kconfig for Arm machines
Date: Thu, 9 May 2019 07:34:09 +0200	[thread overview]
Message-ID: <20a27c22-cd1a-f5a8-9e36-db171c4ae19e@redhat.com> (raw)
In-Reply-To: <CAP+75-XRZ22uhxfLF6uOpjDtKOf_EDC8uGgbu=DgYw-kcBSAGQ@mail.gmail.com>

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é <philmd@redhat.com> 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 <thuth@redhat.com> 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	other threads:[~2019-05-09  5:35 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-07 13:45 [Qemu-devel] [PULL v2 00/28] Kconfig for Arm machines Thomas Huth
2019-05-07 13:45 ` [Qemu-devel] [PULL v2 02/28] hw/ide/ahci: Add a Kconfig switch for the AHCI-ICH9 device Thomas Huth
2019-05-08 15:09 ` [Qemu-devel] [PULL v2 00/28] Kconfig for Arm machines Peter Maydell
2019-05-08 15:33   ` Thomas Huth
2019-05-08 16:43     ` Philippe Mathieu-Daudé
2019-05-08 16:45       ` Philippe Mathieu-Daudé
2019-05-09  5:34         ` Thomas Huth [this message]
2019-05-09  9:32           ` Philippe Mathieu-Daudé
2019-05-09 16:54     ` Peter Maydell
2019-05-09 17:44       ` Philippe Mathieu-Daudé
2019-05-10  7:52       ` Thomas Huth
2019-05-10  9:05         ` Peter Maydell
2019-05-10  8:30       ` Thomas Huth

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=20a27c22-cd1a-f5a8-9e36-db171c4ae19e@redhat.com \
    --to=thuth@redhat.com \
    --cc=jsnow@redhat.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@redhat.com \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@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).