From: "Leonidas P. Papadakos" <papadakospan@gmail.com>
To: patrice.chotard@st.com
Cc: Jose.Abreu@synopsys.com, jayati.sahu@samsung.com,
f.fainelli@gmail.com, heiko@sntech.de, rcsekar@samsung.com,
netdev@vger.kernel.org, sriram.dash@samsung.com,
linux-kernel@vger.kernel.org, p.rajanbabu@samsung.com,
linux-stm32@st-md-mailman.stormreply.com, stable@vger.kernel.org,
pankaj.dubey@samsung.com, peppe.cavallaro@st.com,
davem@davemloft.net, linux-arm-kernel@lists.infradead.org
Subject: Re: [Linux-stm32] [PATCH] net: stmmac: platform: Fix MDIO init for platforms without PHY
Date: Mon, 13 Jan 2020 15:19:20 +0200 [thread overview]
Message-ID: <20200113131920.13273-1-papadakospan@gmail.com> (raw)
In-Reply-To: <c1af466d-0870-364f-1bff-0ac015811e60@st.com>
This change affects my Renegade board (rockchip/rk3328-roc-cc.dtb),
(and probably the very similar Rock64) preventing me from using any kernel after
5.4.6 in a meaningful way.
I get the stacktrace mentioned before at boot.
Predictably, a command like 'ip address show' will hang since it probes
networking but 'sudo' also freezes...
_______________________________________________
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-01-13 13:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20191219102407epcas5p103b26e6fb191f7135d870a3449115c89@epcas5p1.samsung.com>
2019-12-19 10:17 ` [PATCH] net: stmmac: platform: Fix MDIO init for platforms without PHY Padmanabhan Rajanbabu
2019-12-21 5:29 ` David Miller
2020-01-05 20:43 ` Heiko Stübner
2020-01-05 22:22 ` Florian Fainelli
2020-01-05 23:05 ` Heiko Stübner
2020-01-06 20:50 ` Florian Fainelli
2020-01-07 5:34 ` Sriram Dash
2020-01-07 13:15 ` [Linux-stm32] " Patrice CHOTARD
2020-01-07 13:28 ` Patrice CHOTARD
2020-01-13 13:19 ` Leonidas P. Papadakos [this message]
2020-01-13 13:21 ` Jose Abreu
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=20200113131920.13273-1-papadakospan@gmail.com \
--to=papadakospan@gmail.com \
--cc=Jose.Abreu@synopsys.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=heiko@sntech.de \
--cc=jayati.sahu@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=netdev@vger.kernel.org \
--cc=p.rajanbabu@samsung.com \
--cc=pankaj.dubey@samsung.com \
--cc=patrice.chotard@st.com \
--cc=peppe.cavallaro@st.com \
--cc=rcsekar@samsung.com \
--cc=sriram.dash@samsung.com \
--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).