public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Paolo Abeni <pabeni@redhat.com>
To: Sinthu Raja M <sinthu.raja@mistralsolutions.com>,
	Ravi Gunasekaran <r-gunasekaran@ti.com>
Cc: Denis Kirjanov <dkirjanov@suse.de>,
	Siddharth Vadapalli <s-vadapalli@ti.com>,
	 Roger Quadros <rogerq@kernel.org>,
	linux-omap@vger.kernel.org, netdev@vger.kernel.org,
	Sinthu Raja <sinthu.raja@ti.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH V3 1/2] net: ethernet: ti: cpsw_new: enable mac_managed_pm to fix mdio
Date: Thu, 08 Feb 2024 11:27:19 +0100	[thread overview]
Message-ID: <ba0196d4b0f008e146dec58f74142a918ab1986d.camel@redhat.com> (raw)
In-Reply-To: <CAEd-yTSXJdm0GQfA1HxHp7ACaHt7SdhYNepbwLtmc7PJETTzpg@mail.gmail.com>

On Tue, 2024-02-06 at 12:49 +0530, Sinthu Raja M wrote:
> On Tue, Feb 6, 2024 at 11:31 AM Ravi Gunasekaran <r-gunasekaran@ti.com> wrote:
> > In v1, you received a comment to add the fixes tag. The reference stmmac patch also points
> > to this commit as Fixes tag. But as Paolo pointed out in v2, this is not the right
> > fixes tag for your patch series.
> > 
> > I did a git blame on few drivers where PHY is managed by MAC. These have
> > Fixes: fba863b81604 ("net: phy: make PHY PM ops a no-op if MAC driver manages PHY PM")
> 
> Thanks, Ravi for pointing this out.
> But the warning message was caused only after the below commit had been added.
> 744d23c71af3 ("net: phy: Warn about incorrect mdio_bus_phy_resume() state")
> 
> With the below commit the warning didn't pop up.
> fba863b81604 ("net: phy: make PHY PM ops a no-op if MAC driver manages PHY PM")
> That is the reason I have not changed the Fixes tag.
> 
> Let's wait for Paolo's comment on this Fixes: fba863b81604 ("net: phy:
> make PHY PM ops a no-op if MAC driver manages PHY PM")

The main point of fixes tag is helping stable teams to backport the
fixes if and where relevant.

In this case the issue addressed is arguably an inconsistent state,
which may lead to later functional issue. The warning emitted by the
phy core is just an head-up, but it does not look like the 'real'
problem.

An older kernel including fba863b81604 but not including 744d23c71af3
will likely be prone to the issue.

TL;DR: I think it's better to include both fixes tag.

I'll add the 2nd one while applying the patch, no need to repost.

Cheers,

Paolo


  reply	other threads:[~2024-02-08 10:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-06  0:59 [PATCH V3 0/2] CPSW: enable mac_managed_pm to fix mdio Sinthu Raja
2024-02-06  0:59 ` [PATCH V3 1/2] net: ethernet: ti: cpsw_new: " Sinthu Raja
2024-02-06  6:00   ` Ravi Gunasekaran
2024-02-06  7:19     ` Sinthu Raja M
2024-02-08 10:27       ` Paolo Abeni [this message]
2024-02-06  0:59 ` [PATCH V3 2/2] net: ethernet: ti: cpsw: " Sinthu Raja
2024-02-08 11:10 ` [PATCH V3 0/2] CPSW: " patchwork-bot+netdevbpf

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=ba0196d4b0f008e146dec58f74142a918ab1986d.camel@redhat.com \
    --to=pabeni@redhat.com \
    --cc=dkirjanov@suse.de \
    --cc=linux-omap@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=r-gunasekaran@ti.com \
    --cc=rogerq@kernel.org \
    --cc=s-vadapalli@ti.com \
    --cc=sinthu.raja@mistralsolutions.com \
    --cc=sinthu.raja@ti.com \
    --cc=stable@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