devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafał Miłecki" <rafal@milecki.pl>
To: "Arınç ÜNAL" <arinc.unal@arinc9.com>
Cc: Florian Fainelli <f.fainelli@gmail.com>,
	Hauke Mehrtens <hauke@hauke-m.de>,
	Rob Herring <robh+dt@kernel.org>,
	linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
	bcm-kernel-feedback-list@broadcom.com
Subject: Re: [PATCH 2/5] ARM: dts: BCM5301X: Remove cell properties from srab ports on Asus RT-AC88U
Date: Fri, 01 Apr 2022 12:28:11 +0200	[thread overview]
Message-ID: <974a2d22326e921d295a382b13c67b23@milecki.pl> (raw)
In-Reply-To: <20220401102002.15765-2-arinc.unal@arinc9.com>

On 2022-04-01 12:19, Arınç ÜNAL wrote:
> Remove #address-cells and #size-cells properties from the ports node of
> &srab. They are already defined on bcm5301x.dtsi, there's no need to 
> define
> them again.
> 
> Signed-off-by: Arınç ÜNAL <arinc.unal@arinc9.com>

Acked-by: Rafał Miłecki <rafal@milecki.pl>

  reply	other threads:[~2022-04-01 10:48 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-01 10:19 [PATCH 1/5] ARM: dts: BCM5301X: Fix DTC warning for NAND node Arınç ÜNAL
2022-04-01 10:19 ` [PATCH 2/5] ARM: dts: BCM5301X: Remove cell properties from srab ports on Asus RT-AC88U Arınç ÜNAL
2022-04-01 10:28   ` Rafał Miłecki [this message]
2022-04-04 18:35   ` Florian Fainelli
2022-04-01 10:20 ` [PATCH 3/5] ARM: dts: BCM5301X: Add rgmii to port@5 of Broadcom switch " Arınç ÜNAL
2022-04-04 18:36   ` Florian Fainelli
2022-04-01 10:20 ` [PATCH 4/5] ARM: dts: BCM5301X: Retrieve gmac1 MAC address from NVRAM " Arınç ÜNAL
2022-04-01 10:32   ` Rafał Miłecki
2022-04-04 18:36   ` Florian Fainelli
2022-04-01 10:20 ` [PATCH 5/5] ARM: dts: BCM5301X: Disable unused gmac0 and gmac2 " Arınç ÜNAL
2022-04-01 10:40   ` Rafał Miłecki
2022-04-01 11:36     ` Arınç ÜNAL
2022-04-06 18:16       ` Florian Fainelli
2022-04-10  9:20         ` Arınç ÜNAL
2022-04-01 10:27 ` [PATCH 1/5] ARM: dts: BCM5301X: Fix DTC warning for NAND node Rafał Miłecki
2022-04-04 18:35 ` Florian Fainelli

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=974a2d22326e921d295a382b13c67b23@milecki.pl \
    --to=rafal@milecki.pl \
    --cc=arinc.unal@arinc9.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=devicetree@vger.kernel.org \
    --cc=f.fainelli@gmail.com \
    --cc=hauke@hauke-m.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).