From: Baruch Siach <baruch@tkos.co.il>
To: Fabio Estevam <festevam@gmail.com>
Cc: Andrew Lunn <andrew@lunn.ch>,
Russell King - ARM Linux <linux@armlinux.org.uk>,
Soeren Moch <smoch@web.de>,
Steve Twiss <stwiss.opensource@diasemi.com>,
NXP Linux Team <linux-imx@nxp.com>,
Sascha Hauer <kernel@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [RFC] ARM: dts: imx: Fix the AR803X phy-mode
Date: Sun, 31 Mar 2019 06:50:29 +0300 [thread overview]
Message-ID: <87sgv3ln22.fsf@tarshish> (raw)
In-Reply-To: <CAOMZO5CHWBr3x6AfK9Z0bi8msF=qURB26JinMuxFYXvcDg+hyQ@mail.gmail.com>
Hi Fabio,
On Sat, Mar 30 2019, Fabio Estevam wrote:
> On Sat, Mar 30, 2019 at 4:06 PM Baruch Siach <baruch@tkos.co.il> wrote:
>
>> The SolidRun SOM is also affected, I believe (imx6qdl-sr-som.dtsi,
>> AR8035). Would you be able to test it on your side?
>
> This patch does touch imx6qdl-sr-som.dtsi, but I don't have access to
> my Cubox at the moment.
I missed that.
> Could you please test it?
Sure. Tested on Hummingboard2. I verified that networking is broken
without this patch (v5.1-rc2). This patch fixes the problem.
Tested-by: Baruch Siach <baruch@tkos.co.il>
Thanks,
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch@tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
_______________________________________________
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-03-31 3:50 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-30 15:50 [RFC] ARM: dts: imx: Fix the AR803X phy-mode Fabio Estevam
2019-03-30 16:18 ` Andrew Lunn
2019-04-01 12:53 ` Fabio Estevam
2019-03-30 19:06 ` Baruch Siach
2019-03-30 19:11 ` Fabio Estevam
2019-03-31 3:50 ` Baruch Siach [this message]
2019-03-31 10:44 ` Soeren Moch
2019-04-01 8:38 ` Steve Twiss
2019-04-01 12:48 ` Fabio Estevam
2019-04-01 9:01 ` Sébastien Szymanski
2019-04-01 9:05 ` Marc Kleine-Budde
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=87sgv3ln22.fsf@tarshish \
--to=baruch@tkos.co.il \
--cc=andrew@lunn.ch \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux@armlinux.org.uk \
--cc=shawnguo@kernel.org \
--cc=smoch@web.de \
--cc=stwiss.opensource@diasemi.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).