From: Andrew Lunn <andrew@lunn.ch>
To: Jonathan Toppins <jtoppins@redhat.com>
Cc: "Brown, Aaron F" <aaron.f.brown@intel.com>,
"John W. Linville" <linville@tuxdriver.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>
Subject: Re: [Intel-wired-lan] [PATCH] igb: support BCM54616 PHY
Date: Thu, 27 Jul 2017 20:15:41 +0200 [thread overview]
Message-ID: <20170727181541.GB9517@lunn.ch> (raw)
In-Reply-To: <211b5efd-f8d5-cf44-4e0d-dc661c144b7d@redhat.com>
> I recall someone mentioning that there were plans to have phylib support
> [Q]SFP[+] modules as well. I am very interested in that work, if someone
> has patches/plans I would like to take a look.
Hi Jon
The first part was posted yesterday:
https://www.spinics.net/lists/netdev/msg445767.html
Andrew
next prev parent reply other threads:[~2017-07-27 18:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <b5d586566a1b523b9be65567b52898e33058a1cf.1500660210.git.>
2017-07-27 0:40 ` [Intel-wired-lan] [PATCH] igb: support BCM54616 PHY Brown, Aaron F
2017-07-27 15:37 ` Andrew Lunn
2017-07-27 17:41 ` Jonathan Toppins
2017-07-27 18:15 ` Andrew Lunn [this message]
2017-07-27 17:57 ` Florian Fainelli
2017-07-27 18:35 ` Wyborny, Carolyn
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=20170727181541.GB9517@lunn.ch \
--to=andrew@lunn.ch \
--cc=aaron.f.brown@intel.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jtoppins@redhat.com \
--cc=linville@tuxdriver.com \
--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