Please pull u-boot-x86/next to next branch

[Bin Meng]

Hi Tom,

On Tue, Dec 17, 2019 at 8:52 PM Tom Rini <trini at konsulko.com> wrote:
>
> On Sun, Dec 15, 2019 at 09:16:29PM +0800, Bin Meng wrote:
>
> > Hi Tom,
> >
> > This PR includes the following changes for u-boot/next branch.
> >
> > - Various x86 common codes updated for TPL/SPL
> > - I2C designware driver updated for PCI
> > - ICH SPI driver updated to support Apollo Lake
> > - Add Intel FSP2 base support
> > - Intel Apollo Lake platform specific drivers support
> > - Add a new board Google Chromebook Coral
> >
> > The following changes since commit 553cb06887825314e74a9bdac337467c77d1db88:
> >
> >   Merge tag 'dm-next-13dec19' of
> > https://gitlab.denx.de/u-boot/custodians/u-boot-dm into next
> > (2019-12-12 08:18:59 -0500)
> >
> > are available in the git repository at:
> >
> >   https://gitlab.denx.de/u-boot/custodians/u-boot-x86 next
> >
> > for you to fetch changes up to a1d6dc3f84071f05574044f337dbdca70fae495d:
> >
> >   x86: Add chromebook_coral (2019-12-15 11:44:30 +0800)
> >
>
> +(sandbox,sandbox64,sandbox_flattree,sandbox_spl,tools-only) ../drivers/misc/p2sb_emul.c: In function 'sandbox_p2sb_emul_map_physmem':
> +(sandbox,sandbox64,sandbox_flattree,sandbox_spl,tools-only) ../drivers/misc/p2sb_emul.c:236:6: error: 'child' may be used uninitialized in this function [-Werror=maybe-uninitialized]
> +(sandbox,sandbox64,sandbox_flattree,sandbox_spl,tools-only)   ret = axi_read(child, offset, priv->regs, AXI_SIZE_32);
> +(sandbox,sandbox64,sandbox_flattree,sandbox_spl,tools-only)       ^
> +(sandbox,sandbox64,sandbox_flattree,sandbox_spl,tools-only) cc1: all warnings being treated as errors
> +(sandbox,sandbox64,sandbox_flattree,sandbox_spl,tools-only) make[3]: *** [drivers/misc/p2sb_emul.o] Error 1
> +(sandbox,sandbox64,sandbox_flattree,sandbox_spl,tools-only) make[2]: *** [drivers/misc] Error 2
> +(sandbox,sandbox64,sandbox_flattree,sandbox_spl,tools-only) make[1]: *** [drivers] Error 2
>
> Is what I see with this applied, please address, thanks!
>

That's weird. As both GitLab and Azure did not complain anything. See:

https://gitlab.denx.de/u-boot/custodians/u-boot-x86/pipelines/1647
https://dev.azure.com/bmeng/GitHub/_build/results?buildId=146&view=results

Regards,
Bin