From: Vladimir Oltean <olteanv@gmail.com>
To: Michael Walle <michael@walle.cc>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
Andrew Lunn <andrew@lunn.ch>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>
Subject: Re: [PATCH net-next v2 0/2] net: phy: at803x: paging support
Date: Thu, 18 Feb 2021 21:26:47 +0200 [thread overview]
Message-ID: <20210218192647.m5l4wkboxms47urw@skbuf> (raw)
In-Reply-To: <20210218185240.23615-1-michael@walle.cc>
On Thu, Feb 18, 2021 at 07:52:38PM +0100, Michael Walle wrote:
> Add paging support to the QCA AR8031/33 PHY. This will be needed if we
> add support for the .config_inband_aneg callback, see series [1].
>
> The driver itself already accesses the fiber page (without proper locking).
> The former version of this patchset converted the access to
> phy_read_paged(), but Vladimir Oltean mentioned that it is dead code.
> Therefore, the second patch will just remove it.
>
> changes since v1:
> - second patch will remove at803x_aneg_done() altogether
I'm pretty sure net-next is closed now, since David sent the pull
request, and I didn't come to a conclusion yet regarding the final
form of the phy_config_inband_aneg method either.
next prev parent reply other threads:[~2021-02-18 19:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-18 18:52 [PATCH net-next v2 0/2] net: phy: at803x: paging support Michael Walle
2021-02-18 18:52 ` [PATCH net-next v2 1/2] net: phy: at803x: add pages support to AR8031/33 Michael Walle
2021-02-18 18:52 ` [PATCH net-next v2 2/2] net: phy: at803x: remove at803x_aneg_done() Michael Walle
2021-02-18 19:26 ` Vladimir Oltean [this message]
2021-02-18 19:46 ` [PATCH net-next v2 0/2] net: phy: at803x: paging support Michael Walle
2021-02-18 21:08 ` David Miller
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=20210218192647.m5l4wkboxms47urw@skbuf \
--to=olteanv@gmail.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=michael@walle.cc \
--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;
as well as URLs for NNTP newsgroup(s).