linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Mark Rutland <mark.rutland@arm.com>,
	devicetree@vger.kernel.org, Jason Cooper <jason@lakedaemon.net>,
	"Madalin Bucur \(OSS\)" <madalin.bucur@oss.nxp.com>,
	Gregory Clement <gregory.clement@bootlin.com>,
	Rob Herring <robh+dt@kernel.org>,
	linux-arm-kernel@lists.infradead.org,
	Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH] arm64: dts: update SolidRun Armada 8040 phy interface types
Date: Fri, 27 Mar 2020 13:50:46 +0000	[thread overview]
Message-ID: <20200327135046.GN25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <20200327134651.GM25745@shell.armlinux.org.uk>

On Fri, Mar 27, 2020 at 01:46:52PM +0000, Russell King - ARM Linux admin wrote:
> On Fri, Mar 27, 2020 at 02:43:19PM +0100, Andrew Lunn wrote:
> > On Fri, Mar 27, 2020 at 12:40:42PM +0000, Russell King wrote:
> > > Update the SolidRun Armada 8040 platforms phy interface types from the
> > > old 10gbase-kr to the newer and more correct 10gbase-r.
> > > 
> > > Signed-off-by: Russell King <rmk+kernel@armlinux.org.uk>
> > 
> > Reviewed-by: Andrew Lunn <andrew@lunn.ch>
> > 
> > Can we add a fixes: tag to this? So it gets backported to the point
> > 10gbase-r was added.
> 
> I think "carefully" is the answer.  It's not just the point where
> 10gbase-r was added because there's a whole bunch of other patches
> that are also required to the various ethernet and PHY drivers, SFP
> and phylink.  It's probably going to take a bit to work that out,
> get it wrong and stuff will break.

... and actually there is no point.  It is _way_ too soon to even
start thinking of using 10GKR for its true purpose - the patches
to add 10GBASER were only merged for v5.6-rc1, so we're still waiting
for a kernel with that update to be released.  In other words, there's
no stable kernels to backport it to yet.

Do we want it to go into -rc?  If so, it also needs to be thoroughly
tested.

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTC broadband for 0.8mile line in suburbia: sync at 10.2Mbps down 587kbps up

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2020-03-27 13:51 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-27 12:40 [PATCH] arm64: dts: update SolidRun Armada 8040 phy interface types Russell King
2020-03-27 12:42 ` Madalin Bucur (OSS)
2020-03-27 12:45 ` Russell King - ARM Linux admin
2020-03-27 13:43 ` Andrew Lunn
2020-03-27 13:46   ` Russell King - ARM Linux admin
2020-03-27 13:50     ` Russell King - ARM Linux admin [this message]
2020-03-27 14:15       ` Andrew Lunn
2020-03-27 15:17         ` Russell King - ARM Linux admin
2020-03-27 17:16           ` Gregory CLEMENT

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=20200327135046.GN25745@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=andrew@lunn.ch \
    --cc=devicetree@vger.kernel.org \
    --cc=gregory.clement@bootlin.com \
    --cc=jason@lakedaemon.net \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=madalin.bucur@oss.nxp.com \
    --cc=mark.rutland@arm.com \
    --cc=robh+dt@kernel.org \
    --cc=sebastian.hesselbarth@gmail.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).