From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stephen Warren <swarren@wwwdotorg.org>
Date: Tue, 11 Feb 2020 15:02:12 -0700
Subject: FYI: Please pull u-boot-dm
In-Reply-To: <20200211182726.GI13379@bill-the-cat>
References: <CAPnjgZ3d=FUFMs+8ty6yAn8JhpS3KCk6bzx7Tr=68oip090ebg@mail.gmail.com>
 <a289d158-897c-e3ee-f77a-e9f6aa6137c6@wwwdotorg.org>
 <CAPnjgZ3czCQUczGS23gPsn20EncGR4KA1B6bAOB6WMnB7QRZHg@mail.gmail.com>
 <CAPnjgZ3J5JnTq+mF=6G9Tvq8XN8a-RJsibeANMvhLj2k8X=06Q@mail.gmail.com>
 <CAPnjgZ0BrL_3ko_JRHvtmvk8+C6Y81-MjcY-qAfcZJe8khPecw@mail.gmail.com>
 <20200211182726.GI13379@bill-the-cat>
Message-ID: <7adfee9d-5f9a-14eb-9868-798f9495c6b0@wwwdotorg.org>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
To: u-boot@lists.denx.de

On 2/11/20 11:27 AM, Tom Rini wrote:
> On Tue, Feb 11, 2020 at 11:20:36AM -0700, Simon Glass wrote:
>> Hi Tom,
>>
>> On Sat, 8 Feb 2020 at 07:51, Simon Glass <sjg@google.com> wrote:
>>>
>>> Hi Stephen,
>>>
>>> On Thu, 6 Feb 2020 at 15:38, Simon Glass <sjg@google.com> wrote:
>>>>
>>>> Hi Stephen,
>>>>
>>>> On Thu, 6 Feb 2020 at 15:32, Stephen Warren <swarren@wwwdotorg.org> wrote:
>>>>>
>>>>> On 2/6/20 2:55 PM, Simon Glass wrote:
>>>>>> Hi Tom,
>>>>>>
>>>>>> This cannot be pulled yet since we need to update gitlab's docker
>>>>>> image to include SDL2. But gitlab seems to be having various problems
>>>>>> this week and today i won't work at all: ...
>>>>>
>>>>> I see the following build error in u-boot-dm/master via Jenkins:
>>>>>
>>>>>> drivers/misc/p2sb_emul.c: In function ‘sandbox_p2sb_emul_map_physmem’:
>>>>>> drivers/misc/p2sb_emul.c:237:6: warning: ‘child’ may be used uninitialized in this function [-Wmaybe-uninitialized]
>>>>>>    ret = axi_read(child, offset, priv->regs, AXI_SIZE_32);
>>>>>>        ^
>>>>>>    CC      common
>>>>
>>>> Hmmm that's odd. I don't see that, but there are so many device-tree
>>>> and libfdt warnings at present I may have missed it. Will take a look.
>>>
>>> That doesn't happen with my gcc 7.3 toolchain. I'll send a patch to
>>> set child to NULL at the start, but a look at the code shows that it
>>> is correct.
>>>
>>> Also this is in master and was not introduced by this series.
>>
>> A fix for this is going in via the x86 tree.
>>
>> Tom, is there anything else you need from me for this pull request?
> 
> Testing it now, thanks.

Now that this has been merged, the build break has come along with it. 
Is there any chance of picking up the fix from the x86 tree quickly?