forked from marktsai0316/linux
1a998be620
If there are multiple modules with the same name in the same external module tree, there is ambiguity about which one will be loaded, and very likely something odd is happening. Signed-off-by: Masahiro Yamada <masahiroy@kernel.org>
27 lines
427 B
Bash
Executable File
27 lines
427 B
Bash
Executable File
#!/bin/sh
|
|
# SPDX-License-Identifier: GPL-2.0
|
|
|
|
set -e
|
|
|
|
if [ $# != 1 ]; then
|
|
echo "Usage: $0 <modules.order>" >& 2
|
|
exit 1
|
|
fi
|
|
|
|
exit_code=0
|
|
|
|
# Check uniqueness of module names
|
|
check_same_name_modules()
|
|
{
|
|
for m in $(sed 's:.*/::' "$1" | sort | uniq -d)
|
|
do
|
|
echo "error: the following would cause module name conflict:" >&2
|
|
sed -n "/\/$m/s:^: :p" "$1" >&2
|
|
exit_code=1
|
|
done
|
|
}
|
|
|
|
check_same_name_modules "$1"
|
|
|
|
exit $exit_code
|