netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Sverdlin, Alexander" <alexander.sverdlin@siemens.com>
To: "andrew@lunn.ch" <andrew@lunn.ch>
Cc: "linux@armlinux.org.uk" <linux@armlinux.org.uk>,
	"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>,
	"netdev@vger.kernel.org" <netdev@vger.kernel.org>,
	"edumazet@google.com" <edumazet@google.com>,
	"f.fainelli@gmail.com" <f.fainelli@gmail.com>,
	"Haener, Michael" <michael.haener@siemens.com>,
	"kuba@kernel.org" <kuba@kernel.org>
Subject: Re: [PATCH v2 0/3] net: dsa: SERDES support for mv88e632x family
Date: Fri, 14 Jul 2023 08:07:59 +0000	[thread overview]
Message-ID: <5d5092fe89ae0309848db725832e028466186036.camel@siemens.com> (raw)
In-Reply-To: <9edfd9ed-a162-480a-8265-261c2fe72750@lunn.ch>

Hello Andrew,

On Thu, 2023-07-13 at 21:33 +0200, Andrew Lunn wrote:
> On Thu, Jul 13, 2023 at 04:29:12PM +0000, Sverdlin, Alexander wrote:
> > Hi Andrew,
> > 
> > On Thu, 2023-07-13 at 17:34 +0200, Andrew Lunn wrote:
> > > > we did understand Andrew's request indeed, however we were not able to
> > > > backport your series quickly to the version we are able to test on the
> > > > HW.
> > > 
> > > But your own patchset has been tested on net-next by yourself? So it
> > > should be trivial to use "b4 am <threadid>" to get Russells patchset,
> > > apply them on top of net-next, and then add your patches as well.
> > 
> > unfortunately it has been only built on net-next and tested on a 5.15.x with some
> > limited backports so that Russell series would require even more backporting.
> 
> You should indicate that the patch is only built tested when
> submitting it.

yes, it's not tested on the HW with net-net.
It's tested with older kernel with DSA backported to 6.1+ kernel.

> I assume you are using a vendor kernel? What is missing in mainline to
> stop networking working?

If we talk networking, my patch "net: fec: Defer probe if other FEC has deferred MDIO"
comes to my mind, this is quite important, but didn't gain much interest.

But network is usually not the critical part, it's usually other SoC parts and it's
not always easy to plug a Gigabit Switch out and plug it into a HW running fresh kernel.

We are improving on this, but this is a balancing act between being creative on
testing and not upstreaming at all.

-- 
Alexander Sverdlin
Siemens AG
www.siemens.com

  reply	other threads:[~2023-07-14  8:08 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-04  6:59 [PATCH v2 0/3] net: dsa: SERDES support for mv88e632x family M. Haener
2023-07-04  6:59 ` [PATCH v2 1/3] net: dsa: mv88e632x: Refactor serdes read M. Haener
2023-07-04  7:23   ` Sverdlin, Alexander
2023-07-04  6:59 ` [PATCH v2 2/3] net: dsa: mv88e632x: Refactor serdes write M. Haener
2023-07-04  7:23   ` Sverdlin, Alexander
2023-07-04  6:59 ` [PATCH v2 3/3] net: dsa: mv88e632x: Add SERDES ops M. Haener
2023-07-04  7:23   ` Sverdlin, Alexander
2023-07-04  7:17 ` [PATCH v2 0/3] net: dsa: SERDES support for mv88e632x family Haener, Michael
2023-07-04 23:31   ` Andrew Lunn
2023-07-06  6:51     ` Haener, Michael
2023-07-13  6:42       ` Russell King (Oracle)
2023-07-13  7:41         ` Sverdlin, Alexander
2023-07-13 15:34           ` Andrew Lunn
2023-07-13 15:42             ` Russell King (Oracle)
2023-07-13 16:29             ` Sverdlin, Alexander
2023-07-13 19:33               ` Andrew Lunn
2023-07-14  8:07                 ` Sverdlin, Alexander [this message]
2023-07-05 17:31 ` Jakub Kicinski

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=5d5092fe89ae0309848db725832e028466186036.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;
as well as URLs for NNTP newsgroup(s).