devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Edwards <cfsworks@gmail.com>
To: "Florian Fainelli" <florian.fainelli@broadcom.com>,
	"Rafał Miłecki" <rafal@milecki.pl>,
	"William Zhang" <william.zhang@broadcom.com>,
	"Anand Gore" <anand.gore@broadcom.com>,
	"Kursad Oney" <kursad.oney@broadcom.com>
Cc: Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Broadcom internal kernel review list
	<bcm-kernel-feedback-list@broadcom.com>,
	devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Sam Edwards <CFSworks@gmail.com>
Subject: [PATCH v2 0/2] Add support for Zyxel EX3510-B
Date: Wed,  9 Oct 2024 14:54:52 -0700	[thread overview]
Message-ID: <20241009215454.1449508-1-CFSworks@gmail.com> (raw)

Hello BCMBCA maintainers,

This is a second, very minor revision of my previous series for introducing
support for the Zyxel EX3510-B "series," largely motivated by my earlier
patchset [1] that resolves validation errors in the BCMBCA DTs. If checking the
DT, please apply that other patchset first. These changes do not depend on the
other patchset to build correctly or apply cleanly; only to pass validation.

Happy spooky month,
Sam

[1]: https://lore.kernel.org/linux-devicetree/20241009215046.1449389-1-CFSworks@gmail.com/T/

Changes v1->v2:
- Rolled-in commit tags from previous version
- Stylistic change to memory: s/0/0x0
- Delete `range` property from the `nvmem-cells` node, in order to pass DT
  checks.

COMMITTER NOTE: Email being what it is, the capitalization of my email address
is apparently getting discarded. If it is important that the author email
address have identical capitalization to the Signed-off-by, please explain why
so I can investigate why this is happening and/or get these patches to you in a
desired format.

Sam Edwards (2):
  dt-bindings: arm64: bcmbca: Add Zyxel EX3510-B based on BCM4906
  arm64: dts: broadcom: bcmbca: bcm4908: Add DT for Zyxel EX3510-B

 .../bindings/arm/bcm/brcm,bcmbca.yaml         |   1 +
 arch/arm64/boot/dts/broadcom/bcmbca/Makefile  |   1 +
 .../broadcom/bcmbca/bcm4906-zyxel-ex3510b.dts | 196 ++++++++++++++++++
 3 files changed, 198 insertions(+)
 create mode 100644 arch/arm64/boot/dts/broadcom/bcmbca/bcm4906-zyxel-ex3510b.dts

-- 
2.44.2


             reply	other threads:[~2024-10-09 21:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-09 21:54 Sam Edwards [this message]
2024-10-09 21:54 ` [PATCH v2 1/2] dt-bindings: arm64: bcmbca: Add Zyxel EX3510-B based on BCM4906 Sam Edwards
2024-11-24 17:57   ` Florian Fainelli
2024-10-09 21:54 ` [PATCH v2 2/2] arm64: dts: broadcom: bcmbca: bcm4908: Add DT for Zyxel EX3510-B Sam Edwards
2024-11-24 17:57   ` Florian Fainelli
2024-10-10 14:30 ` [PATCH v2 0/2] Add support " Rob Herring (Arm)

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=20241009215454.1449508-1-CFSworks@gmail.com \
    --to=cfsworks@gmail.com \
    --cc=anand.gore@broadcom.com \
    --cc=bcm-kernel-feedback-list@broadcom.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=florian.fainelli@broadcom.com \
    --cc=krzk+dt@kernel.org \
    --cc=kursad.oney@broadcom.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rafal@milecki.pl \
    --cc=robh@kernel.org \
    --cc=william.zhang@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;
as well as URLs for NNTP newsgroup(s).