From: Stanislav Jakubek <stano.jakubek@gmail.com>
To: Florian Fainelli <f.fainelli@gmail.com>
Cc: Florian Fainelli <florian.fainelli@broadcom.com>,
bcm-kernel-feedback-list@broadcom.com,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Ray Jui <rjui@broadcom.com>,
Scott Branden <sbranden@broadcom.com>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/6] ARM: dts: bcm28155-ap: use node labels
Date: Sun, 18 Jun 2023 16:59:33 +0200 [thread overview]
Message-ID: <20230618145933.GA22291@standask-GA-A55M-S2HP> (raw)
In-Reply-To: <e7b68810-e886-c0ca-0a5e-4fa6ac3cd7cd@gmail.com>
On Thu, Jun 08, 2023 at 03:31:28PM -0700, Florian Fainelli wrote:
> On 6/8/23 15:11, Florian Fainelli wrote:
> > From: Florian Fainelli <f.fainelli@gmail.com>
> >
> > On Fri, 26 May 2023 21:30:50 +0200, Stanislav Jakubek <stano.jakubek@gmail.com> wrote:
> > > Use node labels instead of nodename@address for BCM28155 AP board
> > > to simplify its DTS file.
> > >
> > > Signed-off-by: Stanislav Jakubek <stano.jakubek@gmail.com>
> > > ---
> >
> > Applied to https://github.com/Broadcom/stblinux/commits/devicetree/next, thanks!
>
> Dropped that one since the kernel test robot reported build failures, please
> fix and resubmit Stanislav, thanks!
> --
> Florian
>
I'm not actually sure how to fix that. The interaction with the bcm59056.dtsi
seems pretty weird to me. Though I could just be missing some obvious step,
I'm still pretty new at this.
Any hints would be appreciated.
Stanislav
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-06-18 15:00 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-26 19:28 [PATCH 0/6] ARM: dts: bcm-mobile: DT cleanup Stanislav Jakubek
2023-05-26 19:28 ` [PATCH 1/6] ARM: dts: bcm-mobile: change "" includes to <> where applicable Stanislav Jakubek
2023-06-08 22:07 ` Florian Fainelli
2023-05-26 19:29 ` [PATCH 2/6] ARM: dts: bcm21664/23550: use CCU compatibles directly Stanislav Jakubek
2023-06-08 22:09 ` Florian Fainelli
2023-06-08 22:09 ` Florian Fainelli
2023-05-26 19:29 ` [PATCH 3/6] ARM: dts: bcm-mobile: move status properties to the end of nodes Stanislav Jakubek
2023-06-08 22:09 ` Florian Fainelli
2023-05-26 19:30 ` [PATCH 4/6] ARM: dts: bcm11351/21664: add UART, I2C node labels Stanislav Jakubek
2023-06-08 22:10 ` Florian Fainelli
2023-05-26 19:30 ` [PATCH 5/6] ARM: dts: bcm21664-garnet: use " Stanislav Jakubek
2023-06-08 22:10 ` Florian Fainelli
2023-05-26 19:30 ` [PATCH 6/6] ARM: dts: bcm28155-ap: " Stanislav Jakubek
2023-05-27 13:37 ` kernel test robot
2023-06-08 22:11 ` Florian Fainelli
2023-06-08 22:31 ` Florian Fainelli
2023-06-18 14:59 ` Stanislav Jakubek [this message]
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=20230618145933.GA22291@standask-GA-A55M-S2HP \
--to=stano.jakubek@gmail.com \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=florian.fainelli@broadcom.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rjui@broadcom.com \
--cc=robh+dt@kernel.org \
--cc=sbranden@broadcom.com \
/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