From: Heiner Kallweit <hkallweit1@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: andrew@lunn.ch, f.fainelli@gmail.com, khilman@baylibre.com,
vivien.didelot@gmail.com, netdev@vger.kernel.org,
linux-amlogic@lists.infradead.org
Subject: Re: [PATCH net-next 0/3] net: phy: remove genphy_config_init
Date: Fri, 16 Aug 2019 22:02:20 +0200 [thread overview]
Message-ID: <7ca48c8c-80d0-7abc-c0d9-f0ab7f787f04@gmail.com> (raw)
In-Reply-To: <20190816.115754.393902669786330872.davem@davemloft.net>
On 16.08.2019 20:57, David Miller wrote:
> From: Heiner Kallweit <hkallweit1@gmail.com>
> Date: Thu, 15 Aug 2019 14:01:43 +0200
>
>> Supported PHY features are either auto-detected or explicitly set.
>> In both cases calling genphy_config_init isn't needed. All that
>> genphy_config_init does is removing features that are set as
>> supported but can't be auto-detected. Basically it duplicates the
>> code in genphy_read_abilities. Therefore remove genphy_config_init.
>
> Heiner you will need to respin this series as the new adin driver
> added a new call to genphy_config_init().
>
> Thank you.
>
OK, will do. Thanks.
prev parent reply other threads:[~2019-08-16 20:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-15 12:01 [PATCH net-next 0/3] net: phy: remove genphy_config_init Heiner Kallweit
2019-08-15 12:02 ` [PATCH net-next 1/3] net: phy: remove calls to genphy_config_init Heiner Kallweit
2019-08-15 12:03 ` [PATCH net-next 2/3] net: dsa: " Heiner Kallweit
2019-08-15 12:04 ` [PATCH net-next 3/3] net: phy: remove genphy_config_init Heiner Kallweit
2019-08-16 18:57 ` [PATCH net-next 0/3] " David Miller
2019-08-16 20:02 ` Heiner Kallweit [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=7ca48c8c-80d0-7abc-c0d9-f0ab7f787f04@gmail.com \
--to=hkallweit1@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=vivien.didelot@gmail.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).