Received: by 2002:a25:6193:0:0:0:0:0 with SMTP id v141csp1603239ybb; Thu, 2 Apr 2020 04:06:56 -0700 (PDT) X-Google-Smtp-Source: APiQypL1z0TCg+wAhQUxa0/PfJUdYX1aS7z3WBU3Stsbsvy0qm0eoIj+lbq0AJtzgQVWx99BD/36 X-Received: by 2002:a05:6830:10cd:: with SMTP id z13mr409517oto.326.1585825616219; Thu, 02 Apr 2020 04:06:56 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1585825616; cv=none; d=google.com; s=arc-20160816; b=d7Gnqzf2EU5B/zfj6U6vZUPGRn3hS3Fqh33mMeSL9Zv7rOcTCVYNGEba2jVin2chdX 5nYr+0b+hfRO9P3vCqGmz56avdFEqOzJjX+88/DwVF7wVmTooWTKUkYBQemNHOG2qzJI GKknY3/Q9mcIGyt0ynXugn4eYp3FJ65E+nKOutLipW7zLdezxiB7WACcOP+WP4fLb7k3 nhuqXff9LPeZvIKQ785fhfOcvSKrNf887FnoF8B1lZbQc54FS1BRK8h+0kJB5qg67lcl atxBlP8vLJGxRSxuAF/v2gapjsmw0qsRxXATTxmz4GFceC8A0vYNJ+Alt0fSPm3wrCEd EB7A== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject:dkim-signature; bh=tIB72R51lzoNJX57UIZhH59wu8O+hq4911x6tWDtvvM=; b=TV/M2kKfK+/WpKCXCLZAZ8GDVYyVnbo0tcBvhic/3YA35ZiwA04FDCb3LOy7jazxY8 YGOdT1GKbs/daxfTsCEZU8ekkMQjNUTNpaqDeOj0K/8Gvs8k1qhs/eX64eE4R83f+E3W 13rShCBkLBPsRtAjrGzubs9lNrX5X2i3HqMfS+CVMcrmVDRhKqfauuYlW0hX2s4Nqy96 gJw0ESHdFZpUBJBRyTNp/0lJjOX5EVPMjuyQ5msDn8FbhAYzZsWxmVBbZq79noJR7eEV d//Pb1yIYJUEBtHi7GeKZh8zSgalM/sQtkvunrrF89L0sWLn/fVNBCyVPLj1KY7PTf4N NJ6A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=gOwzDAgb; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id l65si2224349oig.156.2020.04.02.04.06.34; Thu, 02 Apr 2020 04:06:56 -0700 (PDT) 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; Authentication-Results: mx.google.com; dkim=pass header.i=@ti.com header.s=ti-com-17Q1 header.b=gOwzDAgb; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=QUARANTINE sp=NONE dis=NONE) header.from=ti.com Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388044AbgDBLGK (ORCPT + 99 others); Thu, 2 Apr 2020 07:06:10 -0400 Received: from lelv0143.ext.ti.com ([198.47.23.248]:56904 "EHLO lelv0143.ext.ti.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388028AbgDBLGK (ORCPT ); Thu, 2 Apr 2020 07:06:10 -0400 Received: from fllv0035.itg.ti.com ([10.64.41.0]) by lelv0143.ext.ti.com (8.15.2/8.15.2) with ESMTP id 032B5mRO043791; Thu, 2 Apr 2020 06:05:48 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ti.com; s=ti-com-17Q1; t=1585825548; bh=tIB72R51lzoNJX57UIZhH59wu8O+hq4911x6tWDtvvM=; h=Subject:To:CC:References:From:Date:In-Reply-To; b=gOwzDAgbuy6A3udlkBX8OS1lDFrDuI3qTrkUUUoUoc1Yt9GM0kjMrSICN2gv/wUlm N+ARrhZGUUrVkkiTymEvE3f/gQ0olYy2JhnxKFZhbQXKqGzmqCM1iDA1vOBRRtxLjN seH14/kjhBenKSX66yfQfWQXgz7tR2iWiqHLX0bM= Received: from DLEE114.ent.ti.com (dlee114.ent.ti.com [157.170.170.25]) by fllv0035.itg.ti.com (8.15.2/8.15.2) with ESMTP id 032B5mcq096678; Thu, 2 Apr 2020 06:05:48 -0500 Received: from DLEE107.ent.ti.com (157.170.170.37) by DLEE114.ent.ti.com (157.170.170.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1847.3; Thu, 2 Apr 2020 06:05:48 -0500 Received: from fllv0039.itg.ti.com (10.64.41.19) by DLEE107.ent.ti.com (157.170.170.37) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1847.3 via Frontend Transport; Thu, 2 Apr 2020 06:05:47 -0500 Received: from [10.250.100.73] (ileax41-snat.itg.ti.com [10.172.224.153]) by fllv0039.itg.ti.com (8.15.2/8.15.2) with ESMTP id 032B5fOW029504; Thu, 2 Apr 2020 06:05:42 -0500 Subject: Re: [PATCH net-next v6 00/11] net: ethernet: ti: add networking support for k3 am65x/j721e soc To: Will Deacon , Nick Desaulniers CC: , , , , , , , , , , , , , , , , References: <20200401.113627.1377328159361906184.davem@davemloft.net> <20200401223500.224253-1-ndesaulniers@google.com> <20200402094239.GA3770@willie-the-truck> From: Grygorii Strashko Message-ID: Date: Thu, 2 Apr 2020 14:05:36 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2 MIME-Version: 1.0 In-Reply-To: <20200402094239.GA3770@willie-the-truck> Content-Type: text/plain; charset="utf-8"; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-EXCLAIMER-MD-CONFIG: e1e8a2fd-e40a-4ac6-ac9b-f7e9cc9ee180 Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/04/2020 12:42, Will Deacon wrote: > On Wed, Apr 01, 2020 at 03:35:00PM -0700, Nick Desaulniers wrote: >>>> I think the ARM64 build is now also broken on Linus' master branch, >>>> after the net-next merge? I am not quite sure if the device tree >>>> patches were supposed to land in mainline the way they did. >>> >>> There's a fix in my net tree and it will go to Linus soon. >>> >>> There is no clear policy for dt change integration, and honestly >>> I try to deal with the situation on a case by case basis. >> >> Yep, mainline aarch64-linux-gnu- builds are totally hosed. DTC fails the build >> very early on: >> https://travis-ci.com/github/ClangBuiltLinux/continuous-integration/jobs/311246218 >> https://travis-ci.com/github/ClangBuiltLinux/continuous-integration/jobs/311246270 >> There was no failure in -next, not sure how we skipped our canary in the coal >> mine. > > Yes, one of the things linux-next does a really good job at catching is > build breakage so it would've been nice to have seen this there rather > than end up with breakage in Linus' tree :( > > Was the timing just bad, or are we missing DT coverage or something else? It seems issue was not caught in -next because the patch that fixes the issue was already in -next before this series was pushed. Sorry for the mess again. -- Best regards, grygorii