kbuild: fix the modules order between drivers and libs
authorMasahiro Yamada <masahiroy@kernel.org>
Sat, 13 Aug 2022 23:09:28 +0000 (08:09 +0900)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 25 Aug 2022 09:40:27 +0000 (11:40 +0200)
commita2cafe242874338c4d9d2a23fb9130c9ae4221d0
tree22dca9431d4fb253f89d0bc16ae36952252833f3
parent8ee44abe4cae06713db33e0a3b1e87bfb95b13ef
kbuild: fix the modules order between drivers and libs

commit 113147510b48e764e624e3d0e6707a1e48bc05a9 upstream.

Commit b2c885549122 ("kbuild: update modules.order only when contained
modules are updated") accidentally changed the modules order.

Prior to that commit, the modules order was determined based on
vmlinux-dirs, which lists core-y/m, drivers-y/m, libs-y/m, in this order.

Now, subdir-modorder lists them in a different order: core-y/m, libs-y/m,
drivers-y/m.

Presumably, there was no practical issue because the modules in drivers
and libs are orthogonal, but there is no reason to have this distortion.

Get back to the original order.

Fixes: b2c885549122 ("kbuild: update modules.order only when contained modules are updated")
Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Makefile