All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Madalin Bucur (OSS)" <madalin.bucur@oss.nxp.com>
To: "maxime.ripard@bootlin.com" <maxime.ripard@bootlin.com>,
	"robh+dt@kernel.org" <robh+dt@kernel.org>,
	"mark.rutland@arm.com" <mark.rutland@arm.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: [RFC] obsolete references to Documentation/devicetree/bindings/net/ethernet.txt
Date: Mon, 23 Dec 2019 09:00:50 +0000	[thread overview]
Message-ID: <VI1PR04MB5567BBD2827A5DDDFD0D82B7EC2E0@VI1PR04MB5567.eurprd04.prod.outlook.com> (raw)

Hi,

this patch removed the ethernet.txt content and added the information found in
it in the ethernet-controller.yaml (Documentation/devicetree/bindings/net):

  commit 9d3de3c58347623b5e71d554628a1571cd3142ad
  Author: Maxime Ripard <maxime.ripard@bootlin.com>
  Date:   Thu Jun 27 17:31:43 2019 +0200

      dt-bindings: net: Add YAML schemas for the generic Ethernet options

      The Ethernet controllers have a good number of generic options that can be
      needed in a device tree. Add a YAML schemas for those.

      Reviewed-by: Rob Herring <robh@kernel.org>
      Signed-off-by: Maxime Ripard <maxime.ripard@bootlin.com>
      Reviewed-by: Andrew Lunn <andrew@lunn.ch>
      Signed-off-by: Rob Herring <robh@kernel.org>

There are still many references to the previous ethernet.txt document:

  $ grep ethernet.txt Documentation/devicetree/bindings/net/ -r | wc -l
  96

Should those be updated too or it's enough to rely on the current content
of the previous ethernet.txt file:

  $ cat Documentation/devicetree/bindings/net/ethernet.txt
  This file has moved to ethernet-controller.yaml.

Thanks,
Madalin

             reply	other threads:[~2019-12-23  9:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-23  9:00 Madalin Bucur (OSS) [this message]
2019-12-26 11:08 ` [RFC] obsolete references to Documentation/devicetree/bindings/net/ethernet.txt Andrew Lunn
2020-01-08 16:24   ` Rob Herring

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=VI1PR04MB5567BBD2827A5DDDFD0D82B7EC2E0@VI1PR04MB5567.eurprd04.prod.outlook.com \
    --to=madalin.bucur@oss.nxp.com \
    --cc=devicetree@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=maxime.ripard@bootlin.com \
    --cc=netdev@vger.kernel.org \
    --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 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.