public inbox for linux-m68k@lists.linux-m68k.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@snapgear.com>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-m68k@lists.linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m68k: drop unused Kconfig symbols
Date: Fri, 21 Oct 2011 15:19:38 +1000	[thread overview]
Message-ID: <4EA100EA.9030503@snapgear.com> (raw)
In-Reply-To: <1319109836.8405.30.camel@x61.thuisdomein>

Thanks Paul, applied.

Regards
Greg


On 20/10/11 21:23, Paul Bolle wrote:
> Reported-by: Geert Uytterhoeven<geert@linux-m68k.org>
> Signed-off-by: Paul Bolle<pebolle@tiscali.nl>
> ---
> "git grep" tested only.
>
>   arch/m68k/Kconfig |   24 +-----------------------
>   1 files changed, 1 insertions(+), 23 deletions(-)
>
> diff --git a/arch/m68k/Kconfig b/arch/m68k/Kconfig
> index 58c6496..3e673ac 100644
> --- a/arch/m68k/Kconfig
> +++ b/arch/m68k/Kconfig
> @@ -163,35 +163,13 @@ config HPAPCI
>   	  If you want to use the internal "APCI" serial ports on an HP400
>   	  machine, say Y here.
>
> -config MVME147_SCC
> -	bool "SCC support for MVME147 serial ports"
> -	depends on MVME147&&  BROKEN
> -	help
> -	  This is the driver for the serial ports on the Motorola MVME147
> -	  boards.  Everyone using one of these boards should say Y here.
> -
> -config MVME162_SCC
> -	bool "SCC support for MVME162 serial ports"
> -	depends on MVME16x&&  BROKEN
> -	help
> -	  This is the driver for the serial ports on the Motorola MVME162 and
> -	  172 boards.  Everyone using one of these boards should say Y here.
> -
> -config BVME6000_SCC
> -	bool "SCC support for BVME6000 serial ports"
> -	depends on BVME6000&&  BROKEN
> -	help
> -	  This is the driver for the serial ports on the BVME4000 and BVME6000
> -	  boards from BVM Ltd.  Everyone using one of these boards should say
> -	  Y here.
> -
>   config DN_SERIAL
>   	bool "Support for DN serial port (dummy)"
>   	depends on APOLLO
>
>   config SERIAL_CONSOLE
>   	bool "Support for serial port console"
> -	depends on (AMIGA || ATARI || SUN3 || SUN3X || VME || APOLLO)&&  (ATARI_MFPSER=y || ATARI_MIDI=y || AMIGA_BUILTIN_SERIAL=y || MULTIFACE_III_TTY=y || SERIAL=y || MVME147_SCC || SERIAL167 || MVME162_SCC || BVME6000_SCC || DN_SERIAL)
> +	depends on (AMIGA || ATARI || SUN3 || SUN3X || VME || APOLLO)&&  (ATARI_MFPSER=y || ATARI_MIDI=y || AMIGA_BUILTIN_SERIAL=y || MULTIFACE_III_TTY=y || SERIAL=y || SERIAL167 || DN_SERIAL)
>   	---help---
>   	  If you say Y here, it will be possible to use a serial port as the
>   	  system console (the system console is the device which receives all


-- 
------------------------------------------------------------------------
Greg Ungerer  --  Principal Engineer        EMAIL:     gerg@snapgear.com
SnapGear Group, McAfee                      PHONE:       +61 7 3435 2888
8 Gardner Close                             FAX:         +61 7 3217 5323
Milton, QLD, 4064, Australia                WEB: http://www.SnapGear.com

      reply	other threads:[~2011-10-21  5:19 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-10-20 11:23 [PATCH] m68k: drop unused Kconfig symbols Paul Bolle
2011-10-21  5:19 ` Greg Ungerer [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=4EA100EA.9030503@snapgear.com \
    --to=gerg@snapgear.com \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=pebolle@tiscali.nl \
    /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