From: Andrew Lunn <andrew@lunn•ch>
To: Phil Elwell <phil@raspberrypi•org>
Cc: Woojung Huh <woojung.huh@microchip•com>,
Microchip Linux Driver Support <UNGLinuxDriver@microchip•com>,
Rob Herring <robh+dt@kernel•org>,
Mark Rutland <mark.rutland@arm•com>,
"David S. Miller" <davem@davemloft•net>,
Mauro Carvalho Chehab <mchehab@kernel•org>,
Greg Kroah-Hartman <gregkh@linuxfoundation•org>,
Linus Walleij <linus.walleij@linaro•org>,
Andrew Morton <akpm@linux-foundation•org>,
Randy Dunlap <rdunlap@infradead•org>,
netdev@vger•kernel.org, devicetree@vger•kernel.org,
linux-kernel@vger•kernel.org, linux-usb@vger•kernel.org
Subject: Re: [PATCH v3 3/3] dt-bindings: Document the DT bindings for lan78xx
Date: Thu, 19 Apr 2018 17:20:56 +0200 [thread overview]
Message-ID: <20180419152056.GD29658@lunn.ch> (raw)
In-Reply-To: <1524148325-78945-5-git-send-email-phil@raspberrypi.org>
On Thu, Apr 19, 2018 at 03:32:05PM +0100, Phil Elwell wrote:
> The Microchip LAN78XX family of devices are Ethernet controllers with
> a USB interface. Despite being discoverable devices it can be useful to
> be able to configure them from Device Tree, particularly in low-cost
> applications without an EEPROM or programmed OTP.
>
> Document the supported properties in a bindings file.
>
> Signed-off-by: Phil Elwell <phil@raspberrypi•org>
Reviewed-by: Andrew Lunn <andrew@lunn•ch>
Andrew
prev parent reply other threads:[~2018-04-19 15:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 14:32 [PATCH v3 0/3] lan78xx: Read configuration from Device Tree Phil Elwell
2018-04-19 14:32 ` Phil Elwell
2018-04-19 14:32 ` [PATCH v3 1/3] lan78xx: Read MAC address from DT if present Phil Elwell
2018-04-19 14:32 ` [PATCH v3 2/3] lan78xx: Read LED states from Device Tree Phil Elwell
2018-04-19 15:19 ` Andrew Lunn
2018-04-19 14:32 ` [PATCH v3 3/3] dt-bindings: Document the DT bindings for lan78xx Phil Elwell
2018-04-19 15:20 ` Andrew Lunn [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=20180419152056.GD29658@lunn.ch \
--to=andrew@lunn$(echo .)ch \
--cc=UNGLinuxDriver@microchip$(echo .)com \
--cc=akpm@linux-foundation$(echo .)org \
--cc=davem@davemloft$(echo .)net \
--cc=devicetree@vger$(echo .)kernel.org \
--cc=gregkh@linuxfoundation$(echo .)org \
--cc=linus.walleij@linaro$(echo .)org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=linux-usb@vger$(echo .)kernel.org \
--cc=mark.rutland@arm$(echo .)com \
--cc=mchehab@kernel$(echo .)org \
--cc=netdev@vger$(echo .)kernel.org \
--cc=phil@raspberrypi$(echo .)org \
--cc=rdunlap@infradead$(echo .)org \
--cc=robh+dt@kernel$(echo .)org \
--cc=woojung.huh@microchip$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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