From: Jakub Kicinski <kuba@kernel.org>
To: linux@armlinux.org.uk
Cc: Ioana Ciornei <ioana.ciornei@nxp.com>,
davem@davemloft.net, edumazet@google.com, pabeni@redhat.com,
netdev@vger.kernel.org, robh+dt@kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH net-next v3 0/4] dt-bindings: net: convert sff,sfp to dtschema
Date: Mon, 11 Jul 2022 15:30:05 -0700 [thread overview]
Message-ID: <20220711153005.315eaa2b@kernel.org> (raw)
In-Reply-To: <20220707091437.446458-1-ioana.ciornei@nxp.com>
On Thu, 7 Jul 2022 12:14:33 +0300 Ioana Ciornei wrote:
> This patch set converts the sff,sfp to dtschema.
>
> The first patch does a somewhat mechanical conversion without changing
> anything else beside the format in which the dt binding is presented.
>
> In the second patch we rename some dt nodes to be generic. The last two
> patches change the GPIO related properties so that they uses the -gpios
> preferred suffix. This way, all the DTBs are passing the validation
> against the sff,sfp.yaml binding.
Looks ready for applying to net-next, if anyone wants to take
the dts changes please speak up now..
next prev parent reply other threads:[~2022-07-11 22:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-07 9:14 [PATCH net-next v3 0/4] dt-bindings: net: convert sff,sfp to dtschema Ioana Ciornei
2022-07-07 9:14 ` [PATCH net-next v3 1/4] " Ioana Ciornei
2022-07-11 19:28 ` Rob Herring
2022-07-07 9:14 ` [PATCH net-next v3 2/4] dt-bindings: net: sff,sfp: rename example dt nodes to be more generic Ioana Ciornei
2022-07-07 9:14 ` [PATCH net-next v3 3/4] arch: arm64: dts: lx2160a-clearfog-itx: rename the sfp GPIO properties Ioana Ciornei
2022-07-07 9:14 ` [PATCH net-next v3 4/4] arch: arm64: dts: marvell: " Ioana Ciornei
2022-07-11 22:30 ` Jakub Kicinski [this message]
2022-07-13 0:40 ` [PATCH net-next v3 0/4] dt-bindings: net: convert sff,sfp to dtschema patchwork-bot+netdevbpf
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=20220711153005.315eaa2b@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=ioana.ciornei@nxp.com \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--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).