From: Shawn Guo <shawnguo@kernel.org>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org,
Rob Herring <robh+dt@kernel.org>, Li Yang <leoyang.li@nxp.com>,
Oleksij Rempel <o.rempel@pengutronix.de>
Subject: Re: [PATCH devicetree 0/3] Update SJA1105 switch RGMII delay bindings
Date: Sun, 21 Nov 2021 10:37:47 +0800 [thread overview]
Message-ID: <20211121023746.GH31998@dragon> (raw)
In-Reply-To: <20211020113613.815210-1-vladimir.oltean@nxp.com>
On Wed, Oct 20, 2021 at 02:36:10PM +0300, Vladimir Oltean wrote:
> The sja1105 driver has received a set of new DT bindings for RGMII
> delays, and it warns when the old ones are in use:
> https://patchwork.kernel.org/project/netdevbpf/cover/20211013222313.3767605-1-vladimir.oltean@nxp.com/
>
> This patch set adds the new bindings to the in-kernel device trees.
> It would be nice if these patches could make it for v5.16, so that we
> don't have warnings in the kernel log.
>
> Vladimir Oltean (3):
> ARM: dts: imx6qp-prtwd3: update RGMII delays for sja1105 switch
> ARM: dts: ls1021a-tsn: update RGMII delays for sja1105 switch
> arm64: dts: lx2160abluebox3: update RGMII delays for sja1105 switch
Applied for 5.16-rc, thanks!
prev parent reply other threads:[~2021-11-21 2:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 11:36 [PATCH devicetree 0/3] Update SJA1105 switch RGMII delay bindings Vladimir Oltean
2021-10-20 11:36 ` [PATCH devicetree 1/3] ARM: dts: imx6qp-prtwd3: update RGMII delays for sja1105 switch Vladimir Oltean
2021-10-20 12:14 ` Oleksij Rempel
2021-10-20 11:36 ` [PATCH devicetree 2/3] ARM: dts: ls1021a-tsn: " Vladimir Oltean
2021-10-20 11:36 ` [PATCH devicetree 3/3] arm64: dts: lx2160abluebox3: " Vladimir Oltean
2021-11-21 2:37 ` Shawn Guo [this message]
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=20211121023746.GH31998@dragon \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=o.rempel@pengutronix.de \
--cc=robh+dt@kernel.org \
--cc=vladimir.oltean@nxp.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).