From: Rakesh Sankaranarayanan <rakesh.sankaranarayanan@microchip.com>
To: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Cc: <woojung.huh@microchip.com>, <UNGLinuxDriver@microchip.com>,
<andrew@lunn.ch>, <f.fainelli@gmail.com>, <olteanv@gmail.com>,
<davem@davemloft.net>, <edumazet@google.com>, <kuba@kernel.org>,
<pabeni@redhat.com>, <arun.ramadoss@microchip.com>,
<hkallweit1@gmail.com>, <linux@armlinux.org.uk>
Subject: [PATCH net 0/2] phy init update and alu table correction
Date: Mon, 16 Jan 2023 15:34:58 +0530 [thread overview]
Message-ID: <20230116100500.614444-1-rakesh.sankaranarayanan@microchip.com> (raw)
This bug-fix patch series contains following changes,
- Update forward table map in ksz9477_fdb_del API.
- Invoke phy init sequence each time of mode update in
lan87xx_config_aneg.
- Execute phy slave init command only if phydev is configured in slave
mode.
Rakesh Sankaranarayanan (2):
net: dsa: microchip: ksz9477: port map correction in ALU table entry
register
net: dsa: microchip: lan937x: run phy initialization during each link
update
drivers/net/dsa/microchip/ksz9477.c | 4 +-
drivers/net/phy/microchip_t1.c | 70 +++++++++++++++++++++++------
2 files changed, 58 insertions(+), 16 deletions(-)
--
2.34.1
next reply other threads:[~2023-01-16 10:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 10:04 Rakesh Sankaranarayanan [this message]
2023-01-16 10:04 ` [PATCH net 1/2] net: dsa: microchip: ksz9477: port map correction in ALU table entry register Rakesh Sankaranarayanan
2023-01-16 20:59 ` Vladimir Oltean
2023-01-16 10:05 ` [PATCH net 2/2] net: dsa: microchip: lan937x: run phy initialization during each link update Rakesh Sankaranarayanan
2023-01-16 22:26 ` Vladimir Oltean
2023-01-19 11:34 ` Rakesh.Sankaranarayanan
2023-01-19 11:36 ` Vladimir Oltean
2023-01-19 17:27 ` Andrew Lunn
2023-01-19 17:35 ` Jakub Kicinski
2023-01-20 10:19 ` Rakesh.Sankaranarayanan
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=20230116100500.614444-1-rakesh.sankaranarayanan@microchip.com \
--to=rakesh.sankaranarayanan@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=andrew@lunn.ch \
--cc=arun.ramadoss@microchip.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=olteanv@gmail.com \
--cc=pabeni@redhat.com \
--cc=woojung.huh@microchip.com \
/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
all inboxes | Powered by JetHome®