From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Jesse Brandeburg <jesse.brandeburg@intel.com>,
Tony Nguyen <anthony.l.nguyen@intel.com>
Cc: Paul Menzel <pmenzel@molgen.mpg.de>,
"David S . Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
intel-wired-lan@lists.osuosl.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Upstream ONL patch for PHY BCM5461S
Date: Tue, 3 Nov 2020 00:13:05 +0100 [thread overview]
Message-ID: <20201102231307.13021-1-pmenzel@molgen.mpg.de> (raw)
Dear Linux folks,
Looking a little bit at Open Network Linux, they carry some Linux
patches, but have not upstreamed them yet. This upstreams support for
the PHY BCM5461S. It’d be great, if you could help review it.
Kind regards,
Paul
Jeffrey Townsend (2):
ethernet: igb: Support PHY BCM5461S
ethernet: igb: e1000_phy: Check for ops.force_speed_duplex existence
drivers/net/ethernet/intel/igb/e1000_82575.c | 23 ++++-
.../net/ethernet/intel/igb/e1000_defines.h | 1 +
drivers/net/ethernet/intel/igb/e1000_hw.h | 1 +
drivers/net/ethernet/intel/igb/e1000_phy.c | 89 +++++++++++++++++--
drivers/net/ethernet/intel/igb/e1000_phy.h | 2 +
drivers/net/ethernet/intel/igb/igb_main.c | 8 ++
6 files changed, 118 insertions(+), 6 deletions(-)
--
2.29.1
next reply other threads:[~2020-11-02 23:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-02 23:13 Paul Menzel [this message]
2020-11-02 23:13 ` [PATCH 1/2] ethernet: igb: Support PHY BCM5461S Paul Menzel
2020-11-02 23:24 ` Paul Menzel
2020-11-03 1:15 ` Florian Fainelli
2020-11-02 23:13 ` [PATCH 2/2] ethernet: igb: e1000_phy: Check for ops.force_speed_duplex existence Paul Menzel
2020-11-03 0:19 ` Jakub Kicinski
2020-11-03 7:35 ` Paul Menzel
2020-11-03 18:39 ` Jakub Kicinski
2021-01-05 17:16 ` Paul Menzel
2021-01-05 17:25 ` Greg KH
2021-01-19 6:55 ` Paul Menzel
2021-01-19 17:05 ` Jakub Kicinski
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=20201102231307.13021-1-pmenzel@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=anthony.l.nguyen@intel.com \
--cc=davem@davemloft.net \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=jesse.brandeburg@intel.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.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;
as well as URLs for NNTP newsgroup(s).