Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Grygorii Strashko <grygorii.strashko@ti.com>
To: Will Deacon <will@kernel.org>,
	Nick Desaulniers <ndesaulniers@google.com>
Cc: devicetree@vger.kernel.org, arnd@arndb.de, robh@kernel.org,
	netdev@vger.kernel.org, t-kristo@ti.com, nsekhar@ti.com,
	linux-kernel@vger.kernel.org, kishon@ti.com,
	peter.ujfalusi@ti.com, clang-built-linux@googlegroups.com,
	m-karicheri2@ti.com, olof@lixom.net, kuba@kernel.org,
	olteanv@gmail.com, davem@davemloft.net,
	linux-arm-kernel@lists.infradead.org, rogerq@ti.com
Subject: Re: [PATCH net-next v6 00/11] net: ethernet: ti: add networking support for k3 am65x/j721e soc
Date: Thu, 2 Apr 2020 14:05:36 +0300	[thread overview]
Message-ID: <adc2aa08-60e2-cdc3-6b5b-6d96f8805c44@ti.com> (raw)
In-Reply-To: <20200402094239.GA3770@willie-the-truck>



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

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-04-02 11:06 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-23 22:52 [PATCH net-next v6 00/11] net: ethernet: ti: add networking support for k3 am65x/j721e soc Grygorii Strashko
2020-03-23 22:52 ` [PATCH net-next v6 01/11] phy: ti: gmii-sel: simplify config dependencies between net drivers and gmii phy Grygorii Strashko
2020-03-23 22:52 ` [PATCH net-next v6 02/11] net: ethernet: ti: ale: fix seeing unreg mcast packets with promisc and allmulti disabled Grygorii Strashko
2020-03-23 22:52 ` [PATCH net-next v6 03/11] net: ethernet: ti: ale: add support for mac-only mode Grygorii Strashko
2020-03-23 22:52 ` [PATCH net-next v6 04/11] net: ethernet: ti: ale: am65: add support for default thread cfg Grygorii Strashko
2020-03-23 22:52 ` [PATCH net-next v6 05/11] dt-binding: ti: am65x: document mcu cpsw nuss Grygorii Strashko
2020-03-23 22:52 ` [PATCH net-next v6 06/11] net: ethernet: ti: introduce am65x/j721e gigabit eth subsystem driver Grygorii Strashko
2020-03-23 22:52 ` [PATCH net-next v6 07/11] arm64: dts: ti: k3-am65-mcu: add cpsw nuss node Grygorii Strashko
2020-03-23 22:52 ` [PATCH net-next v6 08/11] arm64: dts: k3-am654-base-board: add mcu cpsw nuss pinmux and phy defs Grygorii Strashko
2020-03-23 22:52 ` [PATCH net-next v6 09/11] arm64: dts: ti: k3-j721e-mcu: add mcu cpsw nuss node Grygorii Strashko
2020-03-23 22:52 ` [PATCH net-next v6 10/11] arm64: dts: ti: k3-j721e-common-proc-board: add mcu cpsw nuss pinmux and phy defs Grygorii Strashko
2020-03-23 22:52 ` [PATCH net-next v6 11/11] arm64: defconfig: ti: k3: enable dma and networking Grygorii Strashko
2020-03-27  3:01 ` [PATCH net-next v6 00/11] net: ethernet: ti: add networking support for k3 am65x/j721e soc David Miller
2020-03-28  1:53   ` Vladimir Oltean
2020-03-30  7:15     ` Tero Kristo
2020-03-30  7:36       ` Sekhar Nori
2020-03-30  8:28         ` Sekhar Nori
2020-03-30 18:14           ` Grygorii Strashko
2020-04-01 18:27             ` Vladimir Oltean
2020-04-01 18:36               ` David Miller
2020-04-01 22:35                 ` Nick Desaulniers
2020-04-02  9:42                   ` Will Deacon
2020-04-02 11:05                     ` Grygorii Strashko [this message]
2020-04-02 17:27                       ` Nick Desaulniers
2020-04-03  5:11                         ` Sekhar Nori

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=adc2aa08-60e2-cdc3-6b5b-6d96f8805c44@ti.com \
    --to=grygorii.strashko@ti.com \
    --cc=arnd@arndb.de \
    --cc=clang-built-linux@googlegroups.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=kishon@ti.com \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m-karicheri2@ti.com \
    --cc=ndesaulniers@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=nsekhar@ti.com \
    --cc=olof@lixom.net \
    --cc=olteanv@gmail.com \
    --cc=peter.ujfalusi@ti.com \
    --cc=robh@kernel.org \
    --cc=rogerq@ti.com \
    --cc=t-kristo@ti.com \
    --cc=will@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox