Re: [PATCH 3/4] net: mvmdio: print warning when orion-mdio has too many clocks

Hi, Thank you for the patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v5.2-rc7 next-20190705] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/j

Re: [PATCH 3/4] net: mvmdio: print warning when orion-mdio has too many clocks

Hi Andrew, Am 06.07.19 um 18:09 schrieb Andrew Lunn: > On Sat, Jul 06, 2019 at 05:18:59PM +0200, jo...@solid-run.com wrote: >> From: Josua Mayer >> >> Print a warning when device tree specifies more than the maximum of four >> clocks supported by orion-mdio. Because reading from mdio can lock up

Re: [PATCH 3/4] net: mvmdio: print warning when orion-mdio has too many clocks

On Sat, Jul 06, 2019 at 05:18:59PM +0200, jo...@solid-run.com wrote: > From: Josua Mayer > > Print a warning when device tree specifies more than the maximum of four > clocks supported by orion-mdio. Because reading from mdio can lock up > the Armada 8k when a required clock is not initialized, i

[PATCH 3/4] net: mvmdio: print warning when orion-mdio has too many clocks

From: Josua Mayer Print a warning when device tree specifies more than the maximum of four clocks supported by orion-mdio. Because reading from mdio can lock up the Armada 8k when a required clock is not initialized, it is important to notify the user when a specified clock is ignored. Signed-of