[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20200401223500.224253-1-ndesaulniers@google.com>
Date: Wed, 1 Apr 2020 15:35:00 -0700
From: Nick Desaulniers <ndesaulniers@...gle.com>
To: davem@...emloft.net
Cc: arnd@...db.de, devicetree@...r.kernel.org,
grygorii.strashko@...com, kishon@...com, kuba@...nel.org,
linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
m-karicheri2@...com, netdev@...r.kernel.org, nsekhar@...com,
olof@...om.net, olteanv@...il.com, peter.ujfalusi@...com,
robh@...nel.org, rogerq@...com, t-kristo@...com,
clang-built-linux@...glegroups.com
Subject: Re: [PATCH net-next v6 00/11] net: ethernet: ti: add networking
support for k3 am65x/j721e soc
>> 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.
Powered by blists - more mailing lists