From: David Miller <davem@davemloft.net>
To: phil@raspberrypi.org
Cc: woojung.huh@microchip.com, UNGLinuxDriver@microchip.com,
robh+dt@kernel.org, mark.rutland@arm.com, andrew@lunn.ch,
f.fainelli@gmail.com, mchehab@kernel.org,
gregkh@linuxfoundation.org, linus.walleij@linaro.org,
akpm@linux-foundation.org, rdunlap@infradead.org,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH v4 0/3] lan78xx: Read configuration from Device Tree
Date: Fri, 20 Apr 2018 11:39:27 -0400 (EDT) [thread overview]
Message-ID: <20180420.113927.810364321398349353.davem@davemloft.net> (raw)
In-Reply-To: <1524157180-27276-1-git-send-email-phil@raspberrypi.org>
From: Phil Elwell <phil@raspberrypi.org>
Date: Thu, 19 Apr 2018 17:59:37 +0100
> 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.
>
> This patch set adds support for reading the MAC address and LED modes from
> Device Tree.
>
> v4:
> - Rename nodes in bindings doc.
>
> v3:
> - Move LED setting into PHY driver.
>
> v2:
> - Use eth_platform_get_mac_address.
> - Support up to 4 LEDs, and move LED mode constants into dt-bindings header.
> - Improve bindings document.
> - Remove EEE support.
Series applied, thanks Phil.
prev parent reply other threads:[~2018-04-20 15:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 16:59 [PATCH v4 0/3] lan78xx: Read configuration from Device Tree Phil Elwell
2018-04-19 16:59 ` [PATCH v4 1/3] lan78xx: Read MAC address from DT if present Phil Elwell
2018-04-19 16:59 ` [PATCH v4 2/3] lan78xx: Read LED states from Device Tree Phil Elwell
2018-04-19 16:59 ` [PATCH v4 3/3] dt-bindings: Document the DT bindings for lan78xx Phil Elwell
2018-04-20 15:39 ` David Miller [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=20180420.113927.810364321398349353.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=UNGLinuxDriver@microchip.com \
--cc=akpm@linux-foundation.org \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=mchehab@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=phil@raspberrypi.org \
--cc=rdunlap@infradead.org \
--cc=robh+dt@kernel.org \
--cc=woojung.huh@microchip.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 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).