From: Andrew Lunn <andrew@lunn.ch>
To: Fabio Estevam <festevam@gmail.com>
Cc: "moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
Baruch Siach <baruch@tkos.co.il>,
Russell King - ARM Linux <linux@armlinux.org.uk>,
stable <stable@vger.kernel.org>, Soeren Moch <smoch@web.de>,
Steve Twiss <stwiss.opensource@diasemi.com>,
NXP Linux Team <linux-imx@nxp.com>,
Sascha Hauer <kernel@pengutronix.de>,
Marc Kleine-Budde <mkl@pengutronix.de>,
Shawn Guo <shawnguo@kernel.org>,
Michael Grzeschik <mgr@pengutronix.de>
Subject: Re: [PATCH] ARM: dts: imx: Fix the AR803X phy-mode
Date: Tue, 2 Apr 2019 15:21:22 +0200 [thread overview]
Message-ID: <20190402132122.GA15657@lunn.ch> (raw)
In-Reply-To: <CAOMZO5DWcckLSbAmAG2dc5oCgz6z54g4N1mqf3hYX8O7rDY+UQ@mail.gmail.com>
> The fix for KSZ9021 would require some explanation as to what commit
> exposed or caused the issue and would be better to be on a separate
> patch.
+1
Looking at the commit log for that driver, i don't see a patch which
would cause issues like this.
So a clear explanation is required.
Andrew
_______________________________________________
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 14:31 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 [this message]
2019-04-03 6:40 ` Michael Grzeschik
2019-04-08 10:44 ` Michael Grzeschik
2019-04-02 15:48 ` Sasha Levin
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=20190402132122.GA15657@lunn.ch \
--to=andrew@lunn.ch \
--cc=baruch@tkos.co.il \
--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=mgr@pengutronix.de \
--cc=mkl@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=smoch@web.de \
--cc=stable@vger.kernel.org \
--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).