From: "Sverdlin, Alexander" <alexander.sverdlin@siemens.com>
To: "linux@armlinux.org.uk" <linux@armlinux.org.uk>
Cc: "andrew@lunn.ch" <andrew@lunn.ch>,
"olteanv@gmail.com" <olteanv@gmail.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"pabeni@redhat.com" <pabeni@redhat.com>,
"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
"kuba@kernel.org" <kuba@kernel.org>,
"edumazet@google.com" <edumazet@google.com>,
"Haener, Michael" <michael.haener@siemens.com>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCH v3 3/3] net: dsa: mv88e632x: Add SERDES ops
Date: Tue, 18 Jul 2023 08:57:52 +0000 [thread overview]
Message-ID: <98187b6bea1e3f27feadfcf378abb9e99c4b5ee3.camel@siemens.com> (raw)
In-Reply-To: <ZLZQXYvJXl44v7MN@shell.armlinux.org.uk>
Hi Russell,
On Tue, 2023-07-18 at 09:42 +0100, Russell King (Oracle) wrote:
> > > > You need to modify drivers/net/dsa/mv88e6xxx/pcs-6352.c for that.
> > >
> > > ... and this is why you need to be able to test on recent kernels!
> >
> > are you absolutely sure about it?
>
> Yes.
>
> > mv88e6352_serdes_get_stats() remained in serdes.c after your rework and
> > as I see it, your rework is about link status, but you didn't touch
> > registers and statistics.
>
> What I said was:
>
> "but you're not actually driving them at all in terms of reading their
> status or configuring them"
>
> I was not commenting on obtaining statistics, but the status/control
> of the blocks, which is now in the PCS drivers.
>
> So, right now it looks to me that _all_ this series is doing is
> providing support to read statistics from the PCS blocks and nothing
> more, so the cover message for this series is misleading. It is not
> adding support for the serdes blocks. It is only adding support for
> reading statistics from the serdes blocks.
>
> Either correct the patch series to do what the cover message says it's
> doing, or change the cover message to properly describe what the series
> is doing. It needs to be consistent.
thank you, now I see it, .pcs_ops is indeed missing.
And you are right there is no way around it, we will properly port, test
and respin.
--
Alexander Sverdlin
Siemens AG
www.siemens.com
next prev parent reply other threads:[~2023-07-18 8:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-18 6:59 [PATCH v3 0/3] net: dsa: SERDES support for mv88e632x family M. Haener
2023-07-18 6:59 ` [PATCH v3 1/3] net: dsa: mv88e632x: Refactor serdes read M. Haener
2023-07-18 7:29 ` Sverdlin, Alexander
2023-07-18 6:59 ` [PATCH v3 2/3] net: dsa: mv88e632x: Refactor serdes write M. Haener
2023-07-18 7:30 ` Sverdlin, Alexander
2023-07-18 6:59 ` [PATCH v3 3/3] net: dsa: mv88e632x: Add SERDES ops M. Haener
2023-07-18 7:30 ` Sverdlin, Alexander
2023-07-18 7:47 ` Russell King (Oracle)
2023-07-18 7:48 ` Russell King (Oracle)
2023-07-18 8:24 ` Sverdlin, Alexander
2023-07-18 8:42 ` Russell King (Oracle)
2023-07-18 8:57 ` Sverdlin, Alexander [this message]
2023-07-18 8:24 ` Haener, Michael
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=98187b6bea1e3f27feadfcf378abb9e99c4b5ee3.camel@siemens.com \
--to=alexander.sverdlin@siemens.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=michael.haener@siemens.com \
--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®