From: <Rakesh.Sankaranarayanan@microchip.com>
To: <olteanv@gmail.com>, <kuba@kernel.org>, <andrew@lunn.ch>
Cc: <Arun.Ramadoss@microchip.com>, <linux@armlinux.org.uk>,
<hkallweit1@gmail.com>, <davem@davemloft.net>,
<Woojung.Huh@microchip.com>, <linux-kernel@vger.kernel.org>,
<f.fainelli@gmail.com>, <pabeni@redhat.com>,
<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: Fri, 20 Jan 2023 10:19:33 +0000 [thread overview]
Message-ID: <399c5e0184c9e32ece951f63bfe9d865db290851.camel@microchip.com> (raw)
In-Reply-To: <20230119093526.40dd03b0@kernel.org>
Thanks Vladimir, Andrew and Jakub for the support.
I will resubmit the patch on net-next.
Thanks,
Rakesh S.
On Thu, 2023-01-19 at 09:35 -0800, Jakub Kicinski wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you
> know the content is safe
>
> On Thu, 19 Jan 2023 18:27:52 +0100 Andrew Lunn wrote:
> > > Thanks for pointing this out. Do you think submitting this patch
> > > in
> > > net-next is the right way?
> >
> > I would probably go for net-next. That will give it more soak time
> > to
> > find the next way it is broken....
>
> Either a fix or not a fix :( Meaning - if we opt for net-next
> please drop the Fixes tag.
>
> FWIW Greg promised that if we put some sort of a tag or information
> to delay backporting to stable they will obey it. We should test that
> at some point.
prev parent reply other threads:[~2023-01-20 10:19 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
2023-01-19 17:27 ` Andrew Lunn
2023-01-19 17:35 ` Jakub Kicinski
2023-01-20 10:19 ` Rakesh.Sankaranarayanan [this message]
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=399c5e0184c9e32ece951f63bfe9d865db290851.camel@microchip.com \
--to=rakesh.sankaranarayanan@microchip.com \
--cc=Arun.Ramadoss@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=olteanv@gmail.com \
--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
all inboxes | Powered by JetHome®