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=-3.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no 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 AB298C2B9F4 for ; Fri, 25 Jun 2021 21:09:01 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 8733B6195F for ; Fri, 25 Jun 2021 21:09:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229812AbhFYVLV (ORCPT ); Fri, 25 Jun 2021 17:11:21 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33450 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229776AbhFYVLV (ORCPT ); Fri, 25 Jun 2021 17:11:21 -0400 Received: from mail-qk1-x730.google.com (mail-qk1-x730.google.com [IPv6:2607:f8b0:4864:20::730]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 23580C061766 for ; Fri, 25 Jun 2021 14:09:00 -0700 (PDT) Received: by mail-qk1-x730.google.com with SMTP id o6so20655584qkh.4 for ; Fri, 25 Jun 2021 14:09:00 -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=VLdRoc7Vi4IM7D6gRwT1nkjvCtkNEeCVWYhPl933Vi8=; b=zAzQQv0ICPE04oLtdKaTL0S7BzZmMRVFYbUN9B78/VHOQ0uVFTXu7ES2DzCrD0FeOv KCPu+AkqdaBO/tdT+uJoPHSQljVkLKP57DHiH0wSUuGx8JTMjmJ5RuCec9o0eI1ONbZN MDLVvikhWmf5vTPSfm5BUhHQRVyPJ3E7rf86/l40TpdiTVJ5bdR8Xg3f5H/BteSghjGr EFfB00opYK1mVVQdz0z0dNiW8P7OwD9wJ9DlgqPxCc1Nd/t9QHepOiq1A3fmlR/9zzwY 6bKQ3jJzdAPz5+9m640Bq1RayXhj/g65+5gil7R0WXm06im0f/p643j1Cah4RrUnt3np QkCg== 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=VLdRoc7Vi4IM7D6gRwT1nkjvCtkNEeCVWYhPl933Vi8=; b=G7ZroWEyBpkQRmGj187tZr64UpSjT5Myz6FLNNXVzLsGeoVsJGXmPBtIwfe7XZp0BH JDHlp3Pbb8Q9mTbusV+l9BjJVLvxeC5VwxO3skRymOu/IcfBRroElnPNBu/zGD5NfuyA tt3xp117RCzYPD+VKp5kuryAjbLMcxit5LiRla8kFtse5x2NcoYvTRv2HicOCV/RHlKE OtXiC65fbbdFnZX8EtXpkIcVfiVNrTo4CZQ/iQAu7k12v57aQtEwZyLECTmW62BTjASS qFW+nURAlMr+QrGwTosc6+9uGprEepGqeO01okHDmwpipDm39UI+2KDr99uWgE0ekJ4j 2ybQ== X-Gm-Message-State: AOAM533JNNs0C96l7SOWorJTi3zDHG6AEaflokrNVQ/CMwjoEzJm2flE LLb8TigDjJwsAF4MdHQPPXCt+pzHGyPbNNEpxMwdOg== X-Google-Smtp-Source: ABdhPJz8RXmAmiUSRCqk8ZuTiMA1aejnIwARA3yjPDjW1KEL3FTV/5h1khu/4jvBNS/zmARNAv0bmhgACYCS+wwOK58= X-Received: by 2002:a05:620a:209b:: with SMTP id e27mr2603499qka.300.1624655339214; Fri, 25 Jun 2021 14:08:59 -0700 (PDT) MIME-Version: 1.0 References: <20210624082911.5d013e8c@canb.auug.org.au> <20210624185430.692d4b60@canb.auug.org.au> <20210625084114.4126dd02@canb.auug.org.au> In-Reply-To: <20210625084114.4126dd02@canb.auug.org.au> From: Marcin Wojtas Date: Fri, 25 Jun 2021 23:08:47 +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-next@vger.kernel.org Hi Stephen, pt., 25 cze 2021 o 00:41 Stephen Rothwell napisa=C5= =82(a): > > Hi Marcin, > > On Thu, 24 Jun 2021 16:25:57 +0200 Marcin Wojtas wrote: > > > > 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 > > Yes, I reverted the merge in linux-next only. Would it be possible to re-integrate 'marvell-mdio-ACPI' branch along with the 2 fixes that resolve the reported depmod issue? c88c192dc3ea - net: mdiobus: fix fwnode_mdbiobus_register() fallback case ac53c26433b5 - net: mdiobus: withdraw fwnode_mdbiobus_register The first one is needed to apply the second without conflicts. Best regards, Marcin > > > 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? > > I see others have answered this. >