From: Vladimir Oltean <olteanv@gmail.com>
To: Rakesh.Sankaranarayanan@microchip.com
Cc: andrew@lunn.ch, davem@davemloft.net, pabeni@redhat.com,
hkallweit1@gmail.com, Arun.Ramadoss@microchip.com,
Woojung.Huh@microchip.com, linux-kernel@vger.kernel.org,
linux@armlinux.org.uk, f.fainelli@gmail.com, kuba@kernel.org,
edumazet@google.com, UNGLinuxDriver@microchip.com,
netdev@vger.kernel.org
Subject: Re: [PATCH net 2/2] net: dsa: microchip: lan937x: run phy initialization during each link update
Date: Thu, 19 Jan 2023 13:36:00 +0200 [thread overview]
Message-ID: <20230119113600.xfkkpmdz26og2hn3@skbuf> (raw)
In-Reply-To: <7d72bc330d0ce9e57cc862bec39388b7def8782a.camel@microchip.com>
On Thu, Jan 19, 2023 at 11:34:00AM +0000, Rakesh.Sankaranarayanan@microchip.com wrote:
> Thanks for pointing this out. Do you think submitting this patch in
> net-next is the right way?
Hmm, I guess you could submit it to 'net'.
next prev parent reply other threads:[~2023-01-19 11:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 10:04 [PATCH net 0/2] phy init update and alu table correction Rakesh Sankaranarayanan
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 [this message]
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=20230119113600.xfkkpmdz26og2hn3@skbuf \
--to=olteanv@gmail.com \
--cc=Arun.Ramadoss@microchip.com \
--cc=Rakesh.Sankaranarayanan@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=Woojung.Huh@microchip.com \
--cc=andrew@lunn.ch \
--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=pabeni@redhat.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