From: "Aithal, Srikanth" <sraithal@amd.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>,
hkallweit1@gmail.com, andrew@lunn.ch,
Jakub Kicinski <kuba@kernel.org>
Cc: Linux Next Mailing List <linux-next@vger.kernel.org>,
Linux Regressions <regressions@lists.linux.dev>,
open list <linux-kernel@vger.kernel.org>
Subject: linux-next20240208: tg3 driver nw interfaces not getting configured
Date: Thu, 8 Feb 2024 14:00:46 +0530 [thread overview]
Message-ID: <ce7150b7-b6f1-4635-ba5f-fdfda84a6e2f@amd.com> (raw)
In-Reply-To: <20240208155740.24c6ada7@canb.auug.org.au>
Hi,
On 6.8.0-rc3-next-20240208, the network interfaces are not getting
configured.
I have 'NetXtreme BCM5720 Gigabit Ethernet PCIe'
configuration: autonegotiation=on broadcast=yes driver=tg3
If I revert below commit I am able to get back the interfaces mentioned.
commit 9bc791341bc9a5c22b94889aa37993bb69faa317
Author: Heiner Kallweit <hkallweit1@gmail.com>
Date: Sat Feb 3 22:12:50 2024 +0100
tg3: convert EEE handling to use linkmode bitmaps
Convert EEE handling to use linkmode bitmaps. This prepares for
removing the legacy bitmaps from struct ethtool_keee.
No functional change intended.
Note: The change to mii_eee_cap1_mod_linkmode_t(tp->eee.advertised,
val)
in tg3_phy_autoneg_cfg() isn't completely obvious, but it doesn't
change
the current functionality.
Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
Reviewed-by: Andrew Lunn <andrew@lunn.ch>
Link:
https://lore.kernel.org/r/0652b910-6bcc-421f-8769-38f7dae5037e@gmail.com
Signed-off-by: Jakub Kicinski <kuba@kernel.org>
The same works fine on 6.8.0-rc3-next-20240207.
Thanks,
Srikanth Aithal
sraithal@amd.com
next prev parent reply other threads:[~2024-02-08 8:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-08 4:57 linux-next: Fixes tag needs some work in the netfilter tree Stephen Rothwell
2024-02-08 8:07 ` Jozsef Kadlecsik
2024-02-08 8:30 ` Aithal, Srikanth [this message]
2024-02-08 10:46 ` linux-next20240208: tg3 driver nw interfaces not getting configured Heiner Kallweit
2024-02-08 11:05 ` Aithal, Srikanth
2024-02-08 14:02 ` Heiner Kallweit
2024-02-08 15:28 ` Aithal, Srikanth
2024-02-08 22:18 ` Heiner Kallweit
2024-02-09 3:58 ` Aithal, Srikanth
2024-02-09 13:39 ` Andrew Lunn
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=ce7150b7-b6f1-4635-ba5f-fdfda84a6e2f@amd.com \
--to=sraithal@amd.com \
--cc=andrew@lunn.ch \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=regressions@lists.linux.dev \
--cc=sfr@canb.auug.org.au \
/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