From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Damien Le Moal <damien.lemoal@opensource.wdc.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Linus Walleij <linusw@kernel.org>, Imre Kaloz <kaloz@openwrt.org>,
Krzysztof Halasa <khalasa@piap.pl>,
Miquel Raynal <miquel.raynal@bootlin.com>,
Richard Weinberger <richard@nod.at>,
Vignesh Raghavendra <vigneshr@ti.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Wim Van Sebroeck <wim@linux-watchdog.org>,
Guenter Roeck <linux@roeck-us.net>, Marek Vasut <marex@denx.de>,
Lubomir Rintel <lkundrak@v3.sk>, - <devicetree@vger.kernel.org>,
Marc Zyngier <maz@kernel.org>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mtd@lists.infradead.org, linux-serial@vger.kernel.org,
linux-watchdog@vger.kernel.org
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Subject: [PATCH v2 0/3] dt-bindings: serial/mtd/mc/ata: use MC peripheral props
Date: Fri, 27 Jan 2023 10:32:14 +0100 [thread overview]
Message-ID: <20230127093217.60818-1-krzysztof.kozlowski@linaro.org> (raw)
Hi,
Dependencies
============
I think entire patchset should go via one tree (Rob's). Patch #2 depends on
patch #1. Patch #3 could go separate tree as long as others are in the
linux-next. However for simplicity let's push everything through Rob's DT
tree?
Changelog
=========
This is a v2 of this one patch:
https://lore.kernel.org/linux-devicetree/20230123151302.368277-11-krzysztof.kozlowski@linaro.org/
Changes since v1:
1. Add patches 1 and 2 to fix dt_binding_check and few dtbs_check warnings
Best regards,
Krzysztof
Krzysztof Kozlowski (3):
dt-bindings: intel,ixp4xx-expansion-bus: split out peripheral
properties
dt-bindings: reference MC peripheral properties in relevant devices
dt-bindings: serial: restrict possible child node names
.../ata/intel,ixp4xx-compact-flash.yaml | 1 +
...intel,ixp4xx-expansion-bus-controller.yaml | 64 +--------------
...tel,ixp4xx-expansion-peripheral-props.yaml | 80 +++++++++++++++++++
.../mc-peripheral-props.yaml | 1 +
.../devicetree/bindings/mtd/mtd-physmap.yaml | 1 +
.../devicetree/bindings/serial/8250.yaml | 1 +
.../devicetree/bindings/serial/serial.yaml | 2 +-
.../bindings/watchdog/maxim,max63xx.yaml | 1 +
8 files changed, 87 insertions(+), 64 deletions(-)
create mode 100644 Documentation/devicetree/bindings/memory-controllers/intel,ixp4xx-expansion-peripheral-props.yaml
--
2.34.1
next reply other threads:[~2023-01-27 9:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-27 9:32 Krzysztof Kozlowski [this message]
2023-01-27 9:32 ` [PATCH v2 1/3] dt-bindings: intel,ixp4xx-expansion-bus: split out peripheral properties Krzysztof Kozlowski
2023-01-27 13:23 ` Linus Walleij
2023-01-30 19:12 ` Rob Herring
2023-02-06 8:41 ` Krzysztof Kozlowski
2023-01-27 9:32 ` [PATCH v2 2/3] dt-bindings: reference MC peripheral properties in relevant devices Krzysztof Kozlowski
2023-01-27 13:24 ` Linus Walleij
2023-01-28 0:54 ` Damien Le Moal
2023-01-30 9:24 ` Miquel Raynal
2023-01-27 9:32 ` [PATCH v2 3/3] dt-bindings: serial: restrict possible child node names Krzysztof Kozlowski
2023-01-27 13:29 ` Linus Walleij
2023-01-29 15:48 ` Krzysztof Kozlowski
2023-01-30 22:42 ` Linus Walleij
2023-02-02 10:50 ` [PATCH v2 0/3] dt-bindings: serial/mtd/mc/ata: use MC peripheral props Greg Kroah-Hartman
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=20230127093217.60818-1-krzysztof.kozlowski@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=damien.lemoal@opensource.wdc.com \
--cc=devicetree@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=kaloz@openwrt.org \
--cc=khalasa@piap.pl \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linusw@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-serial@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=lkundrak@v3.sk \
--cc=marex@denx.de \
--cc=maz@kernel.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=robh+dt@kernel.org \
--cc=vigneshr@ti.com \
--cc=wim@linux-watchdog.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).