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 15:17:09 +0000 [thread overview]
Message-ID: <20200327151709.GO25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <20200327141538.GE11004@lunn.ch>
On Fri, Mar 27, 2020 at 03:15:38PM +0100, Andrew Lunn wrote:
> > ... and actually there is no point.
>
> O.K. lets merge these as normal, not as fixes. It is probably too
> late for ARM SoC, so i guess they will get merged next cycle.
Yep, which means that the backplane patches from NXP will have to be
delayed about 20 weeks (about 10 weeks in the arm64 tree before being
merged into 5.8-rc1, and then another 10 weeks before 5.8 is released.)
That's probably not a bad thing, as it'll let us hash out the conflicts
between my PCS patch set and their backplane patches.
--
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
WARNING: multiple messages have this Message-ID (diff)
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 15:17:09 +0000 [thread overview]
Message-ID: <20200327151709.GO25745@shell.armlinux.org.uk> (raw)
In-Reply-To: <20200327141538.GE11004@lunn.ch>
On Fri, Mar 27, 2020 at 03:15:38PM +0100, Andrew Lunn wrote:
> > ... and actually there is no point.
>
> O.K. lets merge these as normal, not as fixes. It is probably too
> late for ARM SoC, so i guess they will get merged next cycle.
Yep, which means that the backplane patches from NXP will have to be
delayed about 20 weeks (about 10 weeks in the arm64 tree before being
merged into 5.8-rc1, and then another 10 weeks before 5.8 is released.)
That's probably not a bad thing, as it'll let us hash out the conflicts
between my PCS patch set and their backplane patches.
--
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
next prev parent reply other threads:[~2020-03-27 15:17 UTC|newest]
Thread overview: 18+ 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:40 ` Russell King
2020-03-27 12:42 ` Madalin Bucur (OSS)
2020-03-27 12:42 ` Madalin Bucur (OSS)
2020-03-27 12:45 ` Russell King - ARM Linux admin
2020-03-27 12:45 ` Russell King - ARM Linux admin
2020-03-27 13:43 ` Andrew Lunn
2020-03-27 13:43 ` Andrew Lunn
2020-03-27 13:46 ` Russell King - ARM Linux admin
2020-03-27 13:46 ` Russell King - ARM Linux admin
2020-03-27 13:50 ` Russell King - ARM Linux admin
2020-03-27 13:50 ` Russell King - ARM Linux admin
2020-03-27 14:15 ` Andrew Lunn
2020-03-27 14:15 ` Andrew Lunn
2020-03-27 15:17 ` Russell King - ARM Linux admin [this message]
2020-03-27 15:17 ` Russell King - ARM Linux admin
2020-03-27 17:16 ` Gregory CLEMENT
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=20200327151709.GO25745@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.