From: Florian Fainelli <f.fainelli@gmail.com>
To: Moritz Fischer <mdf@kernel.org>, andrew@lunn.ch
Cc: hkallweit1@gmail.com, davem@davemloft.net,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH net-next] net: fixed-phy: Add fixed_phy_register_with_gpiod() API
Date: Thu, 7 Feb 2019 09:59:52 -0800 [thread overview]
Message-ID: <44188244-b704-ca3e-aedb-ea0a8bf94772@gmail.com> (raw)
In-Reply-To: <20190207175210.9309-1-mdf@kernel.org>
On 2/7/19 9:52 AM, Moritz Fischer wrote:
> Add fixed_phy_register_with_gpiod() API. It lets users create a
> fixed_phy instance that uses a GPIO descriptor which was obtained
> externally e.g. through platform data.
> This enables platform devices (non-DT based) to use GPIOs for link
> status.
>
> Signed-off-by: Moritz Fischer <mdf@kernel.org>
Reviewed-by: Florian Fainelli <f.fainelli@gmail.com>
Thank you!
--
Florian
prev parent reply other threads:[~2019-02-07 18:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-07 17:52 [PATCH net-next] net: fixed-phy: Add fixed_phy_register_with_gpiod() API Moritz Fischer
2019-02-07 17:59 ` Florian Fainelli [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=44188244-b704-ca3e-aedb-ea0a8bf94772@gmail.com \
--to=f.fainelli@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mdf@kernel.org \
--cc=netdev@vger.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