public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Gregory CLEMENT <gregory.clement@free-electrons.com>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Wilson Ding <dingwei@marvell.com>,
	Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
	Jiri Slaby <jslaby@suse.com>,
	linux-serial@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] serial: Make SERIAL_MVEBU_UART depend on ARCH_MVEBU
Date: Fri, 18 Mar 2016 17:26:47 +0100	[thread overview]
Message-ID: <87mvpvoipk.fsf@free-electrons.com> (raw)
In-Reply-To: <1458305151-6140-1-git-send-email-geert@linux-m68k.org> (Geert Uytterhoeven's message of "Fri, 18 Mar 2016 13:45:51 +0100")

Hi Geert,
 
 On ven., mars 18 2016, Geert Uytterhoeven <geert@linux-m68k.org> wrote:

> Enabling support for the UART on Marvell EBU SoCs only make sense when
> compiling for Marvell EBU SoCs, unless compile-testing.
>
> Signed-off-by: Geert Uytterhoeven <geert@linux-m68k.org>

Acked-by: Gregory CLEMENT <gregory.clement@free-electrons.com>

Thanks,

Gregory

> ---
>  drivers/tty/serial/Kconfig | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/drivers/tty/serial/Kconfig b/drivers/tty/serial/Kconfig
> index 13d4ed6caac4a78b..9ce164db25885009 100644
> --- a/drivers/tty/serial/Kconfig
> +++ b/drivers/tty/serial/Kconfig
> @@ -1604,6 +1604,7 @@ config SERIAL_STM32_CONSOLE
>  
>  config SERIAL_MVEBU_UART
>  	bool "Marvell EBU serial port support"
> +	depends on ARCH_MVEBU || COMPILE_TEST
>  	select SERIAL_CORE
>  	help
>  	  This driver is for Marvell EBU SoC's UART. If you have a machine
> -- 
> 1.9.1
>

-- 
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

      reply	other threads:[~2016-03-18 16:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-18 12:45 [PATCH] serial: Make SERIAL_MVEBU_UART depend on ARCH_MVEBU Geert Uytterhoeven
2016-03-18 16:26 ` Gregory CLEMENT [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87mvpvoipk.fsf@free-electrons.com \
    --to=gregory.clement@free-electrons.com \
    --cc=dingwei@marvell.com \
    --cc=geert@linux-m68k.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jslaby@suse.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-serial@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox