From: Sasha Levin <sashal@kernel.org>
To: Sasha Levin <sashal@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
To: shawnguo@kernel.org
Cc: , baruch@tkos.co.il, stable@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: dts: imx: Fix the AR803X phy-mode
Date: Tue, 02 Apr 2019 15:48:24 +0000 [thread overview]
Message-ID: <20190402154825.A0DBB207E0@mail.kernel.org> (raw)
In-Reply-To: <20190401124730.25814-1-festevam@gmail.com>
Hi,
[This is an automated email]
This commit has been processed because it contains a -stable tag.
The stable tag indicates that it's relevant for the following trees: 4.9+
The bot has tested the following trees: v5.0.5, v4.19.32, v4.14.109, v4.9.166.
v5.0.5: Build OK!
v4.19.32: Failed to apply! Possible dependencies:
29988e867cb1 ("ARM: dts: imx7: Fix memory node duplication")
4edbe6aa46d1 ("ARM: dts: imx7d-pico-pi: Move SoM related part to imx7d-pico.dtsi")
50536c661194 ("ARM: dts: imx7d-pico: Do not harcode the memory size")
v4.14.109: Failed to apply! Possible dependencies:
1bf52b98ae1c ("ARM: dts: imx6sx-sabreauto: add external 24MHz clock source")
221aaa198e70 ("ARM: dts: imx6sx-sabreauto: drop board specific pinctrl container node")
37accf72e04b ("ARM: dts: imx6sx-sabreauto: add fec support")
41bbeadceb03 ("ARM: dts: imx7d-pico-pi: Separate into cpu and baseboard dts")
4edbe6aa46d1 ("ARM: dts: imx7d-pico-pi: Move SoM related part to imx7d-pico.dtsi")
76dc340e7585 ("ARM: dts: imx6qdl: SolidRun: move AR8035 into microsom")
8dccafaa281a ("arm: dts: fix unit-address leading 0s")
99a52450c707 ("ARM: dts: imx7d-pico: Add Wifi support")
d9e246cc2880 ("ARM: dts: imx6sx-sabreauto: add PMIC support")
v4.9.166: Failed to apply! Possible dependencies:
12de44f55dcd ("ARM: dts: imx: Fix Ethernet PHY reset polarity")
1317efa1699f ("ARM: dts: imx6ul: Add DTS for liteSOM module")
13283626c889 ("ARM: dts: imx/vf: Correct license text")
1bf52b98ae1c ("ARM: dts: imx6sx-sabreauto: add external 24MHz clock source")
221aaa198e70 ("ARM: dts: imx6sx-sabreauto: drop board specific pinctrl container node")
23c787a99ff7 ("ARM: dts: imx7d-pico: Add initial support")
26ca8b52d6e1 ("ARM: dts: add support for Turris Omnia")
37accf72e04b ("ARM: dts: imx6sx-sabreauto: add fec support")
3faa1bb2e89c ("ARM: dts: imx: add Boundary Devices Nitrogen6_SOM2 support")
41bbeadceb03 ("ARM: dts: imx7d-pico-pi: Separate into cpu and baseboard dts")
478c9440b328 ("ARM: dts: imx6ul: Add DTS for liteBoard")
4edbe6aa46d1 ("ARM: dts: imx7d-pico-pi: Move SoM related part to imx7d-pico.dtsi")
6df11287f7c9 ("ARM: dts: imx6q: Add Engicam i.CoreM6 Quad/Dual initial support")
76dc340e7585 ("ARM: dts: imx6qdl: SolidRun: move AR8035 into microsom")
8dccafaa281a ("arm: dts: fix unit-address leading 0s")
99a52450c707 ("ARM: dts: imx7d-pico: Add Wifi support")
9daee3076940 ("ARM: dts: imx6q: Add Engicam i.CoreM6 DualLite/Solo initial support")
a58d73340b0e ("ARM: dts: armada-385-synology-ds116: add support for Synology DS116 NAS")
c201369d4aa5 ("ARM: dts: imx6ull: add imx6ull support")
d9e246cc2880 ("ARM: dts: imx6sx-sabreauto: add PMIC support")
fc48e76489fd ("ARM: dts: imx6: Add support for Toradex Colibri iMX6 module")
How should we proceed with this patch?
--
Thanks,
Sasha
_______________________________________________
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:[~2019-04-02 15:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-01 12:47 [PATCH] ARM: dts: imx: Fix the AR803X phy-mode Fabio Estevam
2019-04-01 17:55 ` Michael Grzeschik
2019-04-01 19:47 ` Fabio Estevam
2019-04-02 5:52 ` Michael Grzeschik
2019-04-02 11:06 ` Fabio Estevam
2019-04-02 13:21 ` Andrew Lunn
2019-04-03 6:40 ` Michael Grzeschik
2019-04-08 10:44 ` Michael Grzeschik
2019-04-02 15:48 ` Sasha Levin [this message]
2019-04-02 16:26 ` Fabio Estevam
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=20190402154825.A0DBB207E0@mail.kernel.org \
--to=sashal@kernel.org \
--cc=baruch@tkos.co.il \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=stable@vger.kernel.org \
/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).