[U-Boot] Please pull u-boot-dm

[Bin Meng]

Hi Simon,

On Wed, Nov 7, 2018 at 10:25 AM Simon Glass <sjg at chromium.org> wrote:
>
> Hi Bin,
>
> On 6 November 2018 at 19:22, Bin Meng <bmeng.cn at gmail.com> wrote:
> >
> > Hi Simon,
> >
> > On Wed, Nov 7, 2018 at 10:07 AM Simon Glass <sjg at chromium.org> wrote:
> > >
> > > Hi Bin,
> > >
> > > On 6 November 2018 at 18:04, Bin Meng <bmeng.cn at gmail.com> wrote:
> > > >
> > > > Hi Simon,
> > > >
> > > > On Wed, Nov 7, 2018 at 5:51 AM Simon Glass <sjg at chromium.org> wrote:
> > > > >
> > > > > Hi Tom,
> > > > >
> > > > > The following changes since commit 5ef76e59c12c79d106ebda70b710468aa6bd8b75:
> > > > >
> > > > >   Merge branch 'master' of git://git.denx.de/u-boot-sh (2018-11-04 08:12:21 -0500)
> > > > >
> > > > > are available in the Git repository at:
> > > > >
> > > > >   git://git.denx.de/u-boot-dm.git tags/pull-6-nov-18
> > > > >
> > > > > for you to fetch changes up to 9413033c3d5d2bc44eefd1919c60522598cc1bd6:
> > > > >
> > > > >   cpu: sandbox: Add "u-boot, dm-pre-reloc" for all cpu nodes (2018-11-06 13:56:18 -0700)
> > > > >
> > > > > ----------------------------------------------------------------
> > > > > dm: DM_FLAG_PRE_RELOC fixes for release
> > > > > sandbox CPU fixes for release
> > > > >
> > > >
> > > > What happened to the last PR from u-boot-dm, tag pull-15oct-18? I did
> > > > not see that was merged to u-boot/master. The DM_FLAG_PRE_RELOC clean
> > > > up series should be a follow-up to that tag.
> > >
> > > I abandoned that as I think Tom felt that with the flag problem it was
> > > a bit to late to fix everything.
> > >
> > > If your series relies on that then I think we have a problem...
> >
> > Actually this DM_FLAG_PRE_RELOC clean up series is to make previous
> > series complementary, IOW fix potential issues. Previously Tom
> > rejected that was because that broken Tegra which Stephen reported,
> > and with the clean up series this should be fine.
>
> We are just a week from the release. What is broken if we apply none
> of these patches and pull them in after the release?

I suspect we need revert the patch that is causing all these issues
... If that's the way we prefer to do, I will take a look ...

Regards,
Bin