Searched hist:"8 b22820e" (Results 1 – 5 of 5) sorted by relevance
| /openbmc/linux/arch/m68k/68000/ |
| H A D | m68328.c | 8b22820e Fri Oct 30 09:26:24 CDT 2020 Arnd Bergmann <arnd@arndb.de> m68k: m68328: remove duplicate code
Building a kernel with multiple dragonball based boards
enabled needlessly causes a link failure because of duplicate
config_BSP() functions between the CPU versions.
Avoid that merging the three almost identical files into one,
and hiding the CPU configuration behind the board config.
The pr_info() lines are consolidated in one place.
It is still not possible to run a kernel configured for
more than one board, but at least configurations that can
be selected can also be built now.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Greg Ungerer <gerg@linux-m68k.org>
|
| H A D | Makefile | 8b22820e Fri Oct 30 09:26:24 CDT 2020 Arnd Bergmann <arnd@arndb.de> m68k: m68328: remove duplicate code
Building a kernel with multiple dragonball based boards
enabled needlessly causes a link failure because of duplicate
config_BSP() functions between the CPU versions.
Avoid that merging the three almost identical files into one,
and hiding the CPU configuration behind the board config.
The pr_info() lines are consolidated in one place.
It is still not possible to run a kernel configured for
more than one board, but at least configurations that can
be selected can also be built now.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Greg Ungerer <gerg@linux-m68k.org>
|
| /openbmc/linux/arch/m68k/ |
| H A D | Kconfig.machine | 8b22820e Fri Oct 30 09:26:24 CDT 2020 Arnd Bergmann <arnd@arndb.de> m68k: m68328: remove duplicate code
Building a kernel with multiple dragonball based boards
enabled needlessly causes a link failure because of duplicate
config_BSP() functions between the CPU versions.
Avoid that merging the three almost identical files into one,
and hiding the CPU configuration behind the board config.
The pr_info() lines are consolidated in one place.
It is still not possible to run a kernel configured for
more than one board, but at least configurations that can
be selected can also be built now.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Greg Ungerer <gerg@linux-m68k.org>
|
| H A D | Kconfig.cpu | 8b22820e Fri Oct 30 09:26:24 CDT 2020 Arnd Bergmann <arnd@arndb.de> m68k: m68328: remove duplicate code
Building a kernel with multiple dragonball based boards
enabled needlessly causes a link failure because of duplicate
config_BSP() functions between the CPU versions.
Avoid that merging the three almost identical files into one,
and hiding the CPU configuration behind the board config.
The pr_info() lines are consolidated in one place.
It is still not possible to run a kernel configured for
more than one board, but at least configurations that can
be selected can also be built now.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Greg Ungerer <gerg@linux-m68k.org>
|
| /openbmc/linux/arch/m68k/kernel/ |
| H A D | setup_no.c | 8b22820e Fri Oct 30 09:26:24 CDT 2020 Arnd Bergmann <arnd@arndb.de> m68k: m68328: remove duplicate code
Building a kernel with multiple dragonball based boards
enabled needlessly causes a link failure because of duplicate
config_BSP() functions between the CPU versions.
Avoid that merging the three almost identical files into one,
and hiding the CPU configuration behind the board config.
The pr_info() lines are consolidated in one place.
It is still not possible to run a kernel configured for
more than one board, but at least configurations that can
be selected can also be built now.
Signed-off-by: Arnd Bergmann <arnd@arndb.de>
Signed-off-by: Greg Ungerer <gerg@linux-m68k.org>
|