lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 2 Apr 2020 14:05:36 +0300 From: Grygorii Strashko <grygorii.strashko@...com> To: Will Deacon <will@...nel.org>, Nick Desaulniers <ndesaulniers@...gle.com> CC: <davem@...emloft.net>, <arnd@...db.de>, <devicetree@...r.kernel.org>, <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 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
Powered by blists - more mailing lists