From: "Marek Behún" <kabel@kernel.org>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Chris Packham <chris.packham@alliedtelesis.co.nz>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, robh+dt@kernel.org,
krzysztof.kozlowski+dt@linaro.org, atenart@kernel.org,
thomas.petazzoni@free-electrons.com, f.fainelli@gmail.com,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: net: orion-mdio: Convert to JSON schema
Date: Sat, 7 May 2022 12:29:49 +0200 [thread overview]
Message-ID: <20220507122949.2c929211@thinkpad> (raw)
In-Reply-To: <YnLxv8PbDyBE1ODa@lunn.ch>
On Wed, 4 May 2022 23:35:59 +0200
Andrew Lunn <andrew@lunn.ch> wrote:
> On Wed, May 04, 2022 at 04:36:02PM +1200, Chris Packham wrote:
> > Convert the marvell,orion-mdio binding to JSON schema.
> >
> > Signed-off-by: Chris Packham <chris.packham@alliedtelesis.co.nz>
> > ---
> >
> > Notes:
> > Thomas, Antione & Florian I hope you don't mind me putting you as
> > maintainers of the binding. Between you you've written the majority of
> > the mvmdio.c driver.
>
> I actually think it will be me doing any maintenance work on that
> driver.
>
> > This does throw up the following dtbs_check warnings for turris-mox:
> >
> > arch/arm64/boot/dts/marvell/armada-3720-turris-mox.dtb: mdio@32004: switch0@10:reg: [[16], [0]] is too long
> > From schema: Documentation/devicetree/bindings/net/marvell,orion-mdio.yaml
>
> I assume this is coming from
>
> reg = <0x10 0>;
>
> This is odd. Lets see what Marek Behún has to say.
Looks like a mistake on my part.
Marek
prev parent reply other threads:[~2022-05-07 10:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-04 4:36 [PATCH] dt-bindings: net: orion-mdio: Convert to JSON schema Chris Packham
2022-05-04 21:35 ` Andrew Lunn
2022-05-04 21:44 ` Chris Packham
2022-05-07 10:29 ` Marek Behún [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=20220507122949.2c929211@thinkpad \
--to=kabel@kernel.org \
--cc=andrew@lunn.ch \
--cc=atenart@kernel.org \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@kernel.org \
--cc=thomas.petazzoni@free-electrons.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.