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=-8.7 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, 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 D0CB4C49EA6 for ; Thu, 24 Jun 2021 14:26:20 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id BAFE8613EA for ; Thu, 24 Jun 2021 14:26:20 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231992AbhFXO2i (ORCPT ); Thu, 24 Jun 2021 10:28:38 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43622 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S232110AbhFXO2e (ORCPT ); Thu, 24 Jun 2021 10:28:34 -0400 Received: from mail-qt1-x834.google.com (mail-qt1-x834.google.com [IPv6:2607:f8b0:4864:20::834]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 65687C06175F for ; Thu, 24 Jun 2021 07:26:11 -0700 (PDT) Received: by mail-qt1-x834.google.com with SMTP id w26so4874532qto.13 for ; Thu, 24 Jun 2021 07:26:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=semihalf-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=eF2C5PKSwNIz1Hk6OjorU3qtEfdzoZ8f5y1ZncpfVq4=; b=NtirYk5GcJaWeM5Ci3cQMud1RkVXwj+O2x4lIiPhMHgPAe1npALe96C9De94N/JisN EiZG08HB7muGGuwAXT8p3NaNJmhtZ9FlARgfyYa/rq197xk7gMqTCEyE5OvRJ88/5xU2 h1zzdwG/O0QABXt0U9jvA1bWAcj7bAZuD3+aEr3pmHE0ZhxyzH1XE7kBmF/zy2iq6uka eFNPo4G4b1t7u4ZYkjd8YrMH1WGAYRwo7nvV3OIODo5LXlnReW9ULwbDUGxhSuzSCSPa Oc/5G8hrdP5XPlxNeclr8GgJxMq/LAFwf6FUg1jtcDwuZGhiRypsFBW1/OC4iC9sbUmo uIgw== 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:content-transfer-encoding; bh=eF2C5PKSwNIz1Hk6OjorU3qtEfdzoZ8f5y1ZncpfVq4=; b=S7S8xH9IlIvMzZ8PEMsgwsHjxokucHMVO0gWlYtC0QoH8Xaz50N1nWj4hqW5vr7rLz KSAUCw0eRj/csziH8pp+Th/cpFfCERSWMt2mD2yYPUmH+kGFXRGu60WKF7WQq2xK/Xe7 tJ68a7Ksi0zYSZZOEqV1jCObDUHv4ZO/oC5Vkb0N+CDxZjUqgU3hlChVvi3cHRHOmGYE 9msULlxVIvP+AzIfXRWUA56O8KmEr87alk6i+GYNhAlGvjZP3JhU84Q95CWywQXXjOSi qzGd3KnMAaNUOFtKzMfnDDs876IJwG3GnrR1uuNQMKSWbYCUGKXbWw4IOuN37sYAb3xG eH3A== X-Gm-Message-State: AOAM531dOZXjdJVNEt32/4WExpiJxpMwS7Ls6EfaHJrWbWGdJrCVaWKS wYzGBmafiX/ACsmNZzKlXeo1+u+ngTFWCFMFAvEnwA== X-Google-Smtp-Source: ABdhPJxLgFfzXPHK6vcLL7zpNlT3Q675QmDxZBMaTP9WSGvZAsrzJrmYMlnoGrDXO+85MNogvb4YyEBwonpUcghFD0c= X-Received: by 2002:ac8:57d2:: with SMTP id w18mr5097416qta.306.1624544770432; Thu, 24 Jun 2021 07:26:10 -0700 (PDT) MIME-Version: 1.0 References: <20210624082911.5d013e8c@canb.auug.org.au> <20210624185430.692d4b60@canb.auug.org.au> In-Reply-To: <20210624185430.692d4b60@canb.auug.org.au> From: Marcin Wojtas Date: Thu, 24 Jun 2021 16:25:57 +0200 Message-ID: Subject: Re: linux-next: build failure after merge of the net-next tree To: Stephen Rothwell Cc: Naresh Kamboju , David Miller , Networking , Linux Kernel Mailing List , Linux Next Mailing List , Nathan Chancellor , lkft-triage@lists.linaro.org Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Stephen, czw., 24 cze 2021 o 10:54 Stephen Rothwell napisa=C5= =82(a): > > Hi all, > > On Thu, 24 Jun 2021 11:43:14 +0530 Naresh Kamboju wrote: > > > > On Thu, 24 Jun 2021 at 07:59, Nathan Chancellor wro= te: > > > > > > On Thu, Jun 24, 2021 at 12:46:48AM +0200, Marcin Wojtas wrote: > > > > Hi Stephen, > > > > > > > > czw., 24 cze 2021 o 00:29 Stephen Rothwell n= apisa=C5=82(a): > > > > > > > > > > Hi all, > > > > > > > > > > Today's linux-next build (x86_64 modules_install) failed like thi= s: > > > > > > > > > > depmod: ../tools/depmod.c:1792: depmod_report_cycles_from_root: A= ssertion `is < stack_size' failed. > > > > LKFT test farm found this build error. > > > > Regressions found on mips: > > > > - build/gcc-9-malta_defconfig > > - build/gcc-10-malta_defconfig > > - build/gcc-8-malta_defconfig > > > > depmod: ERROR: Cycle detected: fwnode_mdio -> of_mdio -> fwnode_mdio > > depmod: ERROR: Found 2 modules in dependency cycles! > > make[1]: *** [/builds/linux/Makefile:1875: modules_install] Error 1 > > > > > > Thank you for letting us know. Not sure if related, but I just foun= d > > > > out that this code won't compile for the !CONFIG_FWNODE_MDIO. Below > > > > one-liner fixes it: > > > > > > > > --- a/include/linux/fwnode_mdio.h > > > > +++ b/include/linux/fwnode_mdio.h > > > > @@ -40,7 +40,7 @@ static inline int fwnode_mdiobus_register(struct = mii_bus *bus, > > > > * This way, we don't have to keep compat bits around in dr= ivers. > > > > */ > > > > > > > > - return mdiobus_register(mdio); > > > > + return mdiobus_register(bus); > > > > } > > > > #endif > > > > > > > > I'm curious if this is the case. Tomorrow I'll resubmit with above,= so > > > > I'd appreciate recheck. > > > > This proposed fix did not work. > > > > > Reverting all the patches in that series fixes the issue for me. > > > > Yes. > > Reverting all the (6) patches in that series fixed this build problem. > > > > git log --oneline | head > > 3752a7bfe73e Revert "Documentation: ACPI: DSD: describe additional MAC > > configuration" > > da53528ed548 Revert "net: mdiobus: Introduce fwnode_mdbiobus_register()= " > > 479b72ae8b68 Revert "net/fsl: switch to fwnode_mdiobus_register" > > 92f85677aff4 Revert "net: mvmdio: add ACPI support" > > 3d725ff0f271 Revert "net: mvpp2: enable using phylink with ACPI" > > ffa8c267d44e Revert "net: mvpp2: remove unused 'has_phy' field" > > d61c8b66c840 Add linux-next specific files for 20210623 > > So I have reverted the merge of that topic branch from linux-next for > today. Just to understand correctly - you reverted merge from the local branch (I still see the commits on Dave M's net-next/master). I see a quick solution, but I'm wondering how I should proceed. Submit a correction patch to the mailing lists against the net-next? Or the branch is going to be reverted and I should resubmit everything as v4? Best regards, Marcin