From: David Miller <davem@davemloft.net>
To: zach.brown@ni.com
Cc: f.fainelli@gmail.com, mlindner@marvell.com,
stephen@networkplumber.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, devel@driverdev.osuosl.org,
florian.c.schilhabel@googlemail.com, Larry.Finger@lwfinger.net,
gregkh@linuxfoundation.org, rpurdie@rpsys.net,
j.anaszewski@samsung.com, linux-leds@vger.kernel.org,
andrew@lunn.ch
Subject: Re: [PATCH v5 0/4] Add support for led triggers on phy link state change
Date: Tue, 18 Oct 2016 11:57:07 -0400 (EDT) [thread overview]
Message-ID: <20161018.115707.1632276930668736889.davem@davemloft.net> (raw)
In-Reply-To: <1476719395-28273-1-git-send-email-zach.brown@ni.com>
From: Zach Brown <zach.brown@ni.com>
Date: Mon, 17 Oct 2016 10:49:51 -0500
> Fix skge driver that declared enum contants that conflicted with enum
> constants in linux/leds.h
>
> Create function that encapsulates actions taken during the adjust phy link step
> of phy state changes.
>
> Create function that provides list of speeds currently supported by the phy.
>
> Add support for led triggers on phy link state changes by adding
> a config option. When set the config option will create a set of led triggers
> for each phy device. Users can use the led triggers to represent link state
> changes on the phy.
Ok this looks good enough for now, we can expand and improve upon it
later if necessary.
Series applied, thanks Zach.
prev parent reply other threads:[~2016-10-18 15:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-17 15:49 Zach Brown
2016-10-17 15:49 ` [PATCH v5 1/4] skge: Rename LED_OFF and LED_ON in marvel skge driver to avoid conflicts with leds namespace Zach Brown
2016-10-17 15:49 ` [PATCH v5 2/4] net: phy: Encapsulate actions performed during link state changes into function phy_adjust_link Zach Brown
2016-10-17 15:49 ` [PATCH v5 3/4] net: phy: Create phy_supported_speeds function which lists speeds currently supported by a phydevice Zach Brown
2016-10-17 15:49 ` [PATCH v5 4/4] net: phy: leds: add support for led triggers on phy link state change Zach Brown
2016-10-18 7:13 ` Andrew Lunn
2016-10-18 14:50 ` Zach Brown
2016-10-18 15:57 ` 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=20161018.115707.1632276930668736889.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Larry.Finger@lwfinger.net \
--cc=andrew@lunn.ch \
--cc=devel@driverdev.osuosl.org \
--cc=f.fainelli@gmail.com \
--cc=florian.c.schilhabel@googlemail.com \
--cc=gregkh@linuxfoundation.org \
--cc=j.anaszewski@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mlindner@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=rpurdie@rpsys.net \
--cc=stephen@networkplumber.org \
--cc=zach.brown@ni.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
all inboxes | Powered by JetHome®