From: Rob Herring <robh@kernel.org>
To: Geert Uytterhoeven <geert+renesas@glider.be>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Johan Hovold <johan@kernel.org>,
"David S . Miller" <davem@davemloft.net>,
Sean Wang <sean.wang@mediatek.com>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Matthias Brugger <matthias.bgg@gmail.com>,
devicetree@vger.kernel.org, linux-serial@vger.kernel.org,
linux-renesas-soc@vger.kernel.org
Subject: Re: [PATCH v2 0/2] dt-bindings: serial: Convert generic and slave bindings to json-schema
Date: Thu, 12 Mar 2020 14:35:14 -0500 [thread overview]
Message-ID: <20200312193514.GA19903@bogus> (raw)
In-Reply-To: <20200306090046.8890-1-geert+renesas@glider.be>
On Fri, Mar 06, 2020 at 10:00:44AM +0100, Geert Uytterhoeven wrote:
> Hi Rob, Greg,
>
> This patch series converts the generic serial interface and slave-device
> Device Tree bindings to json-schema.
>
> Changes compared to v1[1]:
> - Update references to serial.txt and slave-device.txt,
> - Fix nodename pattern,
> - Add missing maxItems to *-gpios,
> - Express that uart-has-rtscts and [cr]ts-gpios are
> mutually-exclusive,
> - Drop examples,
> - Allow any child node names,
> - Typo s/connnected/connected/.
>
> This is a dependency for converting more serial DT bindings that will
> refer to properties defined in serial.yaml.
>
> This patch is based on next-20200306, which has a recent change to
> nextqualcomm-bluetooth.txt.
Basing it on next is not too useful. I'm inclined to apply and just drop
what conflicts for me. We can fixup the reference after rc1.
Rob
prev parent reply other threads:[~2020-03-12 19:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-06 9:00 [PATCH v2 0/2] dt-bindings: serial: Convert generic and slave bindings to json-schema Geert Uytterhoeven
2020-03-06 9:00 ` [PATCH v2 1/2] dt-bindings: serial: Convert generic " Geert Uytterhoeven
2020-03-23 19:31 ` Rob Herring
2020-03-06 9:00 ` [PATCH v2 2/2] dt-bindings: serial: Convert slave-device " Geert Uytterhoeven
2020-03-16 9:42 ` Matthias Brugger
2020-03-23 19:32 ` Rob Herring
2020-03-12 19:35 ` Rob Herring [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=20200312193514.GA19903@bogus \
--to=robh@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=geert+renesas@glider.be \
--cc=gregkh@linuxfoundation.org \
--cc=johan@kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux-serial@vger.kernel.org \
--cc=matthias.bgg@gmail.com \
--cc=s.hauer@pengutronix.de \
--cc=sean.wang@mediatek.com \
--cc=shawnguo@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).