From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-5.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id EE5B5C2D0E8 for ; Thu, 26 Mar 2020 12:05:46 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id C7CC720848 for ; Thu, 26 Mar 2020 12:05:46 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="XWORKdbf" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728192AbgCZMFp (ORCPT ); Thu, 26 Mar 2020 08:05:45 -0400 Received: from mail-lj1-f193.google.com ([209.85.208.193]:45068 "EHLO mail-lj1-f193.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728001AbgCZMFp (ORCPT ); Thu, 26 Mar 2020 08:05:45 -0400 Received: by mail-lj1-f193.google.com with SMTP id t17so6081596ljc.12 for ; Thu, 26 Mar 2020 05:05:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=5nNaB9xpgft76kVOrndKIt++4NZQfhxGTzqRhmjvGb4=; b=XWORKdbfk4/82GG2LMt8cw1STtFxI/ISwgvMyK9Jh8wthi51e4JxXSTZ0TJt5vpjBh cO4sttEFEr4uECjeU0J+ooDJoDMx6wLr3W20rvJAV38zSVRH5O9uOVghjhyrb3y5wFFG ilIYGxdeDyUMNNlr6MS/q/1gVYPChOTiPj8C+eqRP3RXb5i1iGN9COC/whQnMn5vK/tS CVE7dMk0B9XObUIEAgeGtTVCRMlctuW8IkjDv7F1NSZ2zxdQKIRsbTsZAxY7DkXQt1Qw IlWCh6R+pjDQfAdEcNyKTQn3orSJ8spu7mBrhwkAIwQ+ke5fQZRV+HgzJwsp8srg4GKA Xa2g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=5nNaB9xpgft76kVOrndKIt++4NZQfhxGTzqRhmjvGb4=; b=o5djKHJUixILtUYEcJqc8rlQM/VC3oPqa/LDqfzpGNWNrvrFWNKa0hpD0pYlC9EBa+ xlTYJTTBH6wQTwFAxz0AYr8iaESbe3zZqvtNfGu0K80ix08NSQB4Z80N5SRrMHLkjWEU e3i/+2uytXb1zpP7YB1aUMbDZx75HQprS12U4KO8Hd/U/XrnWckbHshp1FsjQZOypJCp P9TUj8gR6lzW39Ts/Ogn77k4wSDv3HqqbbKb9OYijD6ZT+O0xlpQYLuqxJvjL4ufPdbo WCClz5ISsrY6DB31oy/HIToNm8dy8D+4utmM4tRFTfRQ7isz6kUCMiVuzGonTDV8Fdf0 kA2Q== X-Gm-Message-State: ANhLgQ1B9wUmgwXGX+gfIP82H6/0yyXtNSnR+4Wo43IZt+KCaFa0Z4qE gh5ecQoy2GvaG5D2fSkdQDuAMBZgTyWIEiXQyB2NXQ== X-Google-Smtp-Source: APiQypKOfvEhGwJX5+841/969FmwKYQ7PXm91S/4oiS1EpNSe8epGsQl/snZwjFZRDTJT3zfulTzEHZLNqv043QbqsY= X-Received: by 2002:a2e:730e:: with SMTP id o14mr4992253ljc.273.1585224342806; Thu, 26 Mar 2020 05:05:42 -0700 (PDT) MIME-Version: 1.0 References: <20200326205025.7cdf0d4e@canb.auug.org.au> In-Reply-To: <20200326205025.7cdf0d4e@canb.auug.org.au> From: Anders Roxell Date: Thu, 26 Mar 2020 13:05:31 +0100 Message-ID: Subject: Re: linux-next: Tree for Mar 26 To: Stephen Rothwell , enric.balletbo@collabora.com, Matthias Brugger Cc: Linux Next Mailing List , Linux Kernel Mailing List Content-Type: text/plain; charset="UTF-8" Sender: linux-next-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-next@vger.kernel.org On Thu, 26 Mar 2020 at 10:50, Stephen Rothwell 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