Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <20200326205025.7cdf0d4e@canb.auug.org.au>
In-Reply-To: <20200326205025.7cdf0d4e@canb.auug.org.au>
From:   Anders Roxell <anders.roxell@linaro.org>
Date:   Thu, 26 Mar 2020 13:05:31 +0100
Message-ID: <CADYN=9+u3NY8MES7GihA1o_E0OdpRFtBDRBs5dxb4VeDoWO4+A@mail.gmail.com>
Subject: Re: linux-next: Tree for Mar 26
To:     Stephen Rothwell <sfr@canb.auug.org.au>,
        enric.balletbo@collabora.com,
        Matthias Brugger <matthias.bgg@gmail.com>
Cc:     Linux Next Mailing List <linux-next@vger.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Thu, 26 Mar 2020 at 10:50, Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> Hi all,
>
> Changes since 20200325:
>
> The net-next tree gained a conflict against the net tree.
>
> The input tree still had its build failure for which I disabled a driver.
>
> The tip tree gained a semantic conflict against the battery tree.
>
> The irqchip tree still had its build failure for which I reverted
> 2 commits.
>
> The rcu tree gained a conflict against the spdx tree.
>
> The kvm tree gained a conflict against the spdx tree.
>
> The drivers-x86 tree gained a conflict against the tip tree.
>
> The akpm tree lost a patch that turned up elsewhere.
>
> Non-merge commits (relative to Linus' tree): 10806
>  9415 files changed, 417170 insertions(+), 204705 deletions(-)
>
> ----------------------------------------------------------------------------
>
> I have created today's linux-next tree at
> git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
> (patches at http://www.kernel.org/pub/linux/kernel/next/ ).  If you
> are tracking the linux-next tree using git, you should not use "git pull"
> to do so as that will try to merge the new linux-next release with the
> old one.  You should use "git fetch" and checkout or reset to the new
> master.
>
> You can see which trees have been included by looking in the Next/Trees
> file in the source.  There are also quilt-import.log and merge.log
> files in the Next directory.  Between each merge, the tree was built
> with a ppc64_defconfig for powerpc, an allmodconfig for x86_64, a
> multi_v7_defconfig for arm and a native build of tools/perf. After
> the final fixups (if any), I do an x86_64 modules_install followed by
> builds for x86_64 allnoconfig, powerpc allnoconfig (32 and 64 bit),
> ppc44x_defconfig, allyesconfig and pseries_le_defconfig and i386, sparc
> and sparc64 defconfig and htmldocs. And finally, a simple boot test
> of the powerpc pseries_le_defconfig kernel in qemu (with and without
> kvm enabled).
>
> Below is a summary of the state of the merge.
>
> I am currently merging 316 trees (counting Linus' and 78 trees of bug
> fix patches pending for the current merge release).
>
> Stats about the size of the tree over time can be seen at
> http://neuling.org/linux-next-size.html .
>
> Status of my local build tests will be at
> http://kisskb.ellerman.id.au/linux-next .  If maintainers want to give
> advice about cross compilers/configs that work, we are always open to add
> more builds.
>
> Thanks to Randy Dunlap for doing many randconfig builds.  And to Paul
> Gortmaker for triage and bug fixes.

When building todays tag on arm64 I see this error, CONFIG_DRM_MEDIATEK=m

ERROR: modpost: "mtk_mmsys_ddp_disconnect"
[drivers/gpu/drm/mediatek/mediatek-drm.ko] undefined!
ERROR: modpost: "mtk_mmsys_ddp_connect"
[drivers/gpu/drm/mediatek/mediatek-drm.ko] undefined!
make[2]: *** [../scripts/Makefile.modpost:94: __modpost] Error 1
make[1]: *** [/linux/Makefile:1299: modules] Error 2
make: *** [Makefile:180: sub-make] Error 2

I think this is the problematic patch:
396c3fccaf03 ("soc / drm: mediatek: Move routing control to mmsys device")

Cheers,
Anders