From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: "Marek Behún" <kabel@kernel.org>
Cc: netdev@vger.kernel.org, davem@davemloft.net,
Andrew Lunn <andrew@lunn.ch>
Subject: Re: [PATCH net-next v2 0/5] Support for RollBall 10G copper SFP modules
Date: Fri, 30 Oct 2020 15:01:38 +0000 [thread overview]
Message-ID: <20201030150138.GB1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <20201029222509.27201-1-kabel@kernel.org>
A general point: please have me in the To: line rather than the Cc:
line so that I can find emails better; I've just spent quite a while
trying to find this series you posted last night amongst all the
other emails that I'm Cc'd on.
(The difference between To: and Cc: is that you expect those in the To:
header to be the primary recipients who you expect action from, and
those in the Cc: to be secondary recipients for information.)
https://blog.thedigitalgroup.com/to-vs-cc-vs-bcc-how-to-use-them-correctly
https://www.writebetteremails.com/to-cc.htm
https://thinkproductive.co.uk/email-using-cc-bcc-to/
... etc ...
Thanks.
On Thu, Oct 29, 2020 at 11:25:04PM +0100, Marek Behún wrote:
> Hello,
>
> this is v2 of series adding support for RollBall/Hilink SFP modules.
>
> Checked with:
> checkpatch.pl --max-line-length=80
>
> Changes from v1:
> - wrapped to 80 columns as per Russell's request
> - initialization of RollBall MDIO I2C protocol moved from sfp.c to
> mdio-i2c.c as per Russell's request
> - second patch removes the 802.3z check also from phylink_sfp_config
> as suggested by Russell
> - creation/destruction of mdiobus for SFP now occurs before probing
> for PHY/after releasing PHY (as suggested by Russell)
> - the last patch became a little simpler after the above was done
>
> Cc: Andrew Lunn <andrew@lunn.ch>
> Cc: Russell King <rmk+kernel@armlinux.org.uk>
>
> Marek Behún (5):
> net: phy: mdio-i2c: support I2C MDIO protocol for RollBall SFP modules
> net: phylink: allow attaching phy for SFP modules on 802.3z mode
> net: sfp: create/destroy I2C mdiobus before PHY probe/after PHY
> release
> net: phy: marvell10g: change MACTYPE if underlying MAC does not
> support it
> net: sfp: add support for multigig RollBall transceivers
>
> drivers/net/mdio/mdio-i2c.c | 232 +++++++++++++++++++++++++++++++++-
> drivers/net/phy/marvell10g.c | 31 +++++
> drivers/net/phy/phylink.c | 5 +-
> drivers/net/phy/sfp.c | 67 ++++++++--
> include/linux/mdio/mdio-i2c.h | 8 +-
> 5 files changed, 322 insertions(+), 21 deletions(-)
>
>
> base-commit: cd29296fdfca919590e4004a7e4905544f4c4a32
> --
> 2.26.2
>
>
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2020-10-30 15:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-29 22:25 [PATCH net-next v2 0/5] Support for RollBall 10G copper SFP modules Marek Behún
2020-10-29 22:25 ` [PATCH net-next v2 1/5] net: phy: mdio-i2c: support I2C MDIO protocol for RollBall " Marek Behún
2020-10-30 15:20 ` Russell King - ARM Linux admin
2020-10-29 22:25 ` [PATCH net-next v2 2/5] net: phylink: allow attaching phy for SFP modules on 802.3z mode Marek Behún
2020-10-30 16:29 ` Russell King - ARM Linux admin
2020-10-29 22:25 ` [PATCH net-next v2 3/5] net: sfp: create/destroy I2C mdiobus before PHY probe/after PHY release Marek Behún
2020-10-30 16:31 ` Russell King - ARM Linux admin
2020-10-29 22:25 ` [PATCH net-next v2 4/5] net: phy: marvell10g: change MACTYPE if underlying MAC does not support it Marek Behún
2020-10-29 22:25 ` [PATCH net-next v2 5/5] net: sfp: add support for multigig RollBall transceivers Marek Behún
2020-10-30 16:33 ` Russell King - ARM Linux admin
2020-10-30 15:01 ` Russell King - ARM Linux admin [this message]
2020-10-30 15:29 ` [PATCH net-next v2 0/5] Support for RollBall 10G copper SFP modules Vladimir Oltean
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=20201030150138.GB1551@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=kabel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.