[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20170828165031.GD12195@dtor-ws>
Date: Mon, 28 Aug 2017 09:50:31 -0700
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: Alexandre Belloni <alexandre.belloni@...e-electrons.com>
Cc: Greg Ungerer <gerg@...ux-m68k.org>,
Geert Uytterhoeven <geert@...ux-m68k.org>,
linux-m68k@...ts.linux-m68k.org, linux-input@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] input: misc: don't build m68kspkr when mach_beep is
undefined
On Thu, Aug 24, 2017 at 04:44:27PM +0200, Alexandre Belloni wrote:
> mach_beep is defined arch/m68k/kernel/setup_mm.c which is compiled only
> when MMU is selected.
>
> To avoid linking errors, make INPUT_M68K_BEEP depend on MMU.
Hmm, can we maybe pull mach_beep from setup_mm.c to setup.c? MMU
dependency seems to be artificial.
>
> Signed-off-by: Alexandre Belloni <alexandre.belloni@...e-electrons.com>
> ---
> drivers/input/misc/Kconfig | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/input/misc/Kconfig b/drivers/input/misc/Kconfig
> index 3872488c3fd7..7a44f633a413 100644
> --- a/drivers/input/misc/Kconfig
> +++ b/drivers/input/misc/Kconfig
> @@ -178,7 +178,7 @@ config INPUT_SPARCSPKR
>
> config INPUT_M68K_BEEP
> tristate "M68k Beeper support"
> - depends on M68K
> + depends on M68K && MMU
>
> config INPUT_MAX77693_HAPTIC
> tristate "MAXIM MAX77693/MAX77843 haptic controller support"
> --
> 2.14.1
>
Thanks.
--
Dmitry
Powered by blists - more mailing lists