[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <87o9txilh5.fsf@concordia.ellerman.id.au>
Date: Fri, 09 Jun 2017 19:00:54 +1000
From: Michael Ellerman <mpe@...erman.id.au>
To: Liviu Dudau <liviu@...au.co.uk>, David Miller <davem@...emloft.net>
Cc: jon.mason@...adcom.com, andrew@...n.ch, f.fainelli@...il.com,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
bcm-kernel-feedback-list@...adcom.com
Subject: Re: [PATCH net-next] net: phy: use of_mdio_parse_addr
Liviu Dudau <liviu@...au.co.uk> writes:
> On Fri, Jun 02, 2017 at 02:22:51PM -0400, David Miller wrote:
>> From: Jon Mason <jon.mason@...adcom.com>
>> Date: Wed, 31 May 2017 15:43:30 -0400
>>
>> > use of_mdio_parse_addr() in place of an OF read of reg and a bounds
>> > check (which is litterally the exact same thing that
>> > of_mdio_parse_addr() does)
>> >
>> > Signed-off-by: Jon Mason <jon.mason@...adcom.com>
>>
>> Applied, thanks Jon.
>
> This makes linux-next fail the modules_install target as depmod detects 2 circular
> dependencies. Reverting this patch fixes the issue.
>
> depmod: ERROR: Cycle detected: libphy -> of_mdio -> fixed_phy -> libphy
> depmod: ERROR: Cycle detected: libphy -> of_mdio -> libphy
> depmod: ERROR: Found 3 modules in dependency cycles!
> make[1]: *** [/home/dliviu/devel/kernel/Makefile:1245: _modinst_post] Error 1
>
> This is on an ARCH=arm build, build I doubt it makes a difference. Let me know if
> you need some .config values in order to reproduce.
Same happens on 32-bit powerpc.
cheers
Powered by blists - more mailing lists