devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Oleksij Rempel <o.rempel@pengutronix.de>
Cc: netdev <netdev@vger.kernel.org>,
	devicetree@vger.kernel.org, Sascha Hauer <kernel@pengutronix.de>,
	Jakub Kicinski <kuba@kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH net-next v2 2/2] dt-bindings: net: add schema for Microchip/SMSC LAN95xx USB Ethernet controllers
Date: Fri, 11 Feb 2022 10:49:46 -0600	[thread overview]
Message-ID: <YgaTqpmmb67mCdlc@robh.at.kernel.org> (raw)
In-Reply-To: <20220209160252.GB26024@pengutronix.de>

On Wed, Feb 09, 2022 at 05:02:52PM +0100, Oleksij Rempel wrote:
> On Wed, Feb 09, 2022 at 09:38:57AM -0600, Rob Herring wrote:
> > On Wed, Feb 9, 2022 at 9:35 AM Rob Herring <robh@kernel.org> wrote:
> > >
> > > On Wed, 09 Feb 2022 09:10:25 +0100, Oleksij Rempel wrote:
> > > > Create initial schema for Microchip/SMSC LAN95xx USB Ethernet controllers and
> > > > import all currently supported USB IDs form drivers/net/usb/smsc95xx.c
> > > >
> > > > Signed-off-by: Oleksij Rempel <o.rempel@pengutronix.de>
> > > > ---
> > > >  .../bindings/net/microchip,lan95xx.yaml       | 80 +++++++++++++++++++
> > > >  1 file changed, 80 insertions(+)
> > > >  create mode 100644 Documentation/devicetree/bindings/net/microchip,lan95xx.yaml
> > > >
> > >
> > > Running 'make dtbs_check' with the schema in this patch gives the
> > > following warnings. Consider if they are expected or the schema is
> > > incorrect. These may not be new warnings.
> > >
> > > Note that it is not yet a requirement to have 0 warnings for dtbs_check.
> > > This will change in the future.
> > >
> > > Full log is available here: https://patchwork.ozlabs.org/patch/1590223
> > >
> > >
> > > smsc@2: $nodename:0: 'smsc@2' does not match '^ethernet(@.*)?$'
> > >         arch/arm/boot/dts/tegra30-ouya.dt.yaml
> > >
> > > usbether@1: $nodename:0: 'usbether@1' does not match '^ethernet(@.*)?$'
> > >         arch/arm64/boot/dts/broadcom/bcm2837-rpi-3-b.dt.yaml
> > >         arch/arm64/boot/dts/freescale/imx8mm-kontron-n801x-s.dt.yaml
> > >         arch/arm/boot/dts/bcm2835-rpi-b.dt.yaml
> > >         arch/arm/boot/dts/bcm2835-rpi-b-plus.dt.yaml
> > >         arch/arm/boot/dts/bcm2835-rpi-b-rev2.dt.yaml
> > >         arch/arm/boot/dts/bcm2836-rpi-2-b.dt.yaml
> > >         arch/arm/boot/dts/bcm2837-rpi-3-b.dt.yaml
> > >         arch/arm/boot/dts/omap3-beagle-xm-ab.dt.yaml
> > >         arch/arm/boot/dts/omap3-beagle-xm.dt.yaml
> > >         arch/arm/boot/dts/omap4-panda-a4.dt.yaml
> > >         arch/arm/boot/dts/omap4-panda.dt.yaml
> > >         arch/arm/boot/dts/omap4-panda-es.dt.yaml
> > >
> > > usbether@3: $nodename:0: 'usbether@3' does not match '^ethernet(@.*)?$'
> > >         arch/arm/boot/dts/omap5-uevm.dt.yaml
> > 
> > So this binding is already in use, but was undocumented?
> 
> Ack.
> 
> > Or did you forget to remove the .txt file?
> 
> No, there was no documentation.
> 
> > The commit message should highlight all this.
> > 
> > (I don't expect you to fix all these warnings, I was just surprised to
> > see them given this is an 'initial schema'.)
> 
> This patches was create before I needed to use it. Should I resent it
> with new commit message?

Yes, please.

Rob

      reply	other threads:[~2022-02-11 16:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-09  8:10 [PATCH net-next v2 0/2] provide yaml schema for some of USB ethernet controllers Oleksij Rempel
2022-02-09  8:10 ` [PATCH net-next v2 1/2] dt-bindings: net: add schema for ASIX USB Ethernet controllers Oleksij Rempel
2022-02-09 15:35   ` Rob Herring
2022-02-11 16:51   ` Rob Herring
2022-02-09  8:10 ` [PATCH net-next v2 2/2] dt-bindings: net: add schema for Microchip/SMSC LAN95xx " Oleksij Rempel
2022-02-09 15:35   ` Rob Herring
2022-02-09 15:38     ` Rob Herring
2022-02-09 16:02       ` Oleksij Rempel
2022-02-11 16:49         ` 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=YgaTqpmmb67mCdlc@robh.at.kernel.org \
    --to=robh@kernel.org \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=kernel@pengutronix.de \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=o.rempel@pengutronix.de \
    /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).