From: Andrew Lunn <andrew@lunn.ch>
To: Raju Lakkaraju <Raju.Lakkaraju@microsemi.com>
Cc: Rob Herring <robh@kernel.org>,
netdev@vger.kernel.org, devicetree@vger.kernel.org,
f.fainelli@gmail.com, Allan.Nielsen@microsemi.com
Subject: Re: [PATCH v3 net-next] net: phy: Add LED mode driver for Microsemi PHYs.
Date: Thu, 16 Feb 2017 15:19:17 +0100 [thread overview]
Message-ID: <20170216141917.GA17550@lunn.ch> (raw)
In-Reply-To: <20170216090646.GA29082@microsemi.com>
On Thu, Feb 16, 2017 at 02:36:48PM +0530, Raju Lakkaraju wrote:
> Hi Rob,
>
> On Wed, Feb 15, 2017 at 10:45:40AM -0600, Rob Herring wrote:
> > EXTERNAL EMAIL
> >
> >
> > On Tue, Feb 07, 2017 at 07:10:26PM +0530, Raju Lakkaraju wrote:
> > > From: Raju Lakkaraju <Raju.Lakkaraju@microsemi.com>
> > >
> > > + Default value is VSC8531_LINK_1000_ACTIVITY (1).
> > > +- vsc8531,led-1-mode : LED mode. Specify how the LED[1] should behave.
> >
> > You failed to address my comment on v2. vsc8531 is not a vendor prefix.
> > Please fix in a new patch since David already applied it.
> >
>
> Accpeted my fault. i missed your comment.
> Do i need to change from "vsc8531, led-0-mode" to "mscc, led-0-mode"
> Is this your suggestion?
Hi Raju
Are there any in kernel users of this binding? I don't think there
are. I know Microsemi has a modified beagle bone black available as a
development board, but i don't think mainline support for this board
has been added yet?
Since there is nothing to remain backwards compatible with, you could
change all the property names?
Andrew
next prev parent reply other threads:[~2017-02-16 14:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 13:40 [PATCH v3 net-next] net: phy: Add LED mode driver for Microsemi PHYs Raju Lakkaraju
2017-02-08 18:29 ` David Miller
[not found] ` <1486474826-29426-1-git-send-email-Raju.Lakkaraju-dzo6w/eZyo2tG0bUXCXiUA@public.gmane.org>
2017-02-15 16:45 ` Rob Herring
2017-02-16 9:06 ` Raju Lakkaraju
2017-02-16 14:19 ` Andrew Lunn [this message]
[not found] ` <20170216090646.GA29082-dzo6w/eZyo2tG0bUXCXiUA@public.gmane.org>
2017-02-21 16:42 ` Rob Herring
[not found] ` <CAL_JsqJLCe1O7Bv526zAY-s-R1DcnA2O0bpx48dTFGSgeu-Edw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-02-24 6:05 ` Raju Lakkaraju
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=20170216141917.GA17550@lunn.ch \
--to=andrew@lunn.ch \
--cc=Allan.Nielsen@microsemi.com \
--cc=Raju.Lakkaraju@microsemi.com \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=robh@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 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).