From: Vladimir Oltean <olteanv@gmail.com>
To: Marek Vasut <marex@denx.de>
Cc: netdev@vger.kernel.org, "David S. Miller" <davem@davemloft.net>,
Andrew Lunn <andrew@lunn.ch>,
Arun Ramadoss <arun.ramadoss@microchip.com>,
Eric Dumazet <edumazet@google.com>,
Florian Fainelli <f.fainelli@gmail.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Russell King <linux@armlinux.org.uk>,
UNGLinuxDriver@microchip.com,
Woojung Huh <woojung.huh@microchip.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] net: dsa: microchip: Fix gigabit set and get function for KSZ87xx
Date: Thu, 23 Feb 2023 00:31:41 +0200 [thread overview]
Message-ID: <20230222223141.ozeis33beq5wpkfy@skbuf> (raw)
In-Reply-To: <ed05fc85-72a8-e694-b829-731f6d720347@denx.de>
On Wed, Feb 22, 2023 at 11:05:10PM +0100, Marek Vasut wrote:
> On 2/22/23 22:08, Vladimir Oltean wrote:
> > Please summarize in the commit title what is the user-visible impact of
> > the problem that is being fixed. Short and to the point.
>
> Can you suggest a Subject which is acceptable ?
Nope. The thing is, I don't know what you're seeing, only you do. I can
only review and comment if it's plausible or not. I'm sure you can come
up with something.
> > > Currently, the driver uses PORT read function on register P_XMII_CTRL_1
> > > to access the P_GMII_1GBIT_M, i.e. Is_1Gbps, bit.
> >
> > Provably false. The driver does do that, but not for KSZ87xx.
>
> The driver uses port read function with register value 0x56 instead of 0x06
> , which means the remapping happens twice, which provably breaks the driver
> since commit Fixes below .
The sentence is false in the context of ksz87xx, which is what is the
implied context of this patch (see commit title written by yourself).
The P_GMII_1GBIT_M field is not accessed, and that is a bug in itself.
Also, the (lack of) access to the P_GMII_1GBIT_M field is not what
causes the breakage that you see, but to other fields from that register.
> > There is no call site other than ksz_set_xmii(). Please delete false
> > information from the commit message.
>
> $ git grep P_XMII_CTRL_1 drivers/net/dsa/microchip/
> drivers/net/dsa/microchip/ksz_common.c: [P_XMII_CTRL_1] = 0x06,
> drivers/net/dsa/microchip/ksz_common.c: [P_XMII_CTRL_1] = 0x0301,
> drivers/net/dsa/microchip/ksz_common.c: ksz_pread8(dev, port, regs[P_XMII_CTRL_1], &data8);
> drivers/net/dsa/microchip/ksz_common.c: ksz_pwrite8(dev, port, regs[P_XMII_CTRL_1], data8);
> drivers/net/dsa/microchip/ksz_common.c: ksz_pread8(dev, port, regs[P_XMII_CTRL_1], &data8);
> drivers/net/dsa/microchip/ksz_common.c: ksz_pread8(dev, port, regs[P_XMII_CTRL_1], &data8);
> drivers/net/dsa/microchip/ksz_common.c: ksz_pread8(dev, port, regs[P_XMII_CTRL_1], &data8);
> drivers/net/dsa/microchip/ksz_common.c: ksz_pwrite8(dev, port, regs[P_XMII_CTRL_1], data8);
> drivers/net/dsa/microchip/ksz_common.h: P_XMII_CTRL_1,
>
> I count 6.
So your response to 2 reviewers wasting their time to do a detailed
analysis of the code paths that apply to the KSZ87xx model in particular,
to tell you precisely why your commit message is incorrect is "git grep"?
> OK, to make this simple, can you write a commit message which you consider
> acceptable, to close this discussion ?
Nope. The thing is, I'm sure you can, too. Maybe you need to take a
break and think about this some more.
next prev parent reply other threads:[~2023-02-22 22:31 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 3:17 [PATCH] net: dsa: microchip: Fix gigabit set and get function for KSZ87xx Marek Vasut
2023-02-22 3:52 ` Arun.Ramadoss
2023-02-22 12:50 ` Russell King (Oracle)
2023-02-22 13:03 ` Russell King (Oracle)
2023-02-22 15:10 ` Marek Vasut
2023-02-22 15:56 ` Russell King (Oracle)
2023-02-22 16:30 ` Marek Vasut
2023-02-22 16:39 ` Russell King (Oracle)
2023-02-22 18:43 ` Marek Vasut
2023-02-22 19:12 ` Russell King (Oracle)
2023-02-22 21:25 ` Vladimir Oltean
2023-02-22 21:08 ` Vladimir Oltean
2023-02-22 22:05 ` Marek Vasut
2023-02-22 22:31 ` Vladimir Oltean [this message]
2023-02-22 22:58 ` Marek Vasut
2023-02-22 23:05 ` Florian Fainelli
2023-02-22 23:07 ` Russell King (Oracle)
2023-02-22 23:21 ` Vladimir Oltean
2023-02-22 23:55 ` Marek Vasut
2023-02-23 0:22 ` Vladimir Oltean
2023-02-23 5:17 ` Marek Vasut
2023-02-23 14:20 ` Vladimir Oltean
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=20230222223141.ozeis33beq5wpkfy@skbuf \
--to=olteanv@gmail.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=kuba@kernel.org \
--cc=linux@armlinux.org.uk \
--cc=marex@denx.de \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=stable@vger.kernel.org \
--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