All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Ungerer <gerg@uclinux.org>
To: Paul Bolle <pebolle@tiscali.nl>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
	linux-m68k@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m68k: clean up unused "config ROMVECSIZE"
Date: Thu, 21 Mar 2013 15:33:59 +1000	[thread overview]
Message-ID: <514A9BC7.2010201@uclinux.org> (raw)
In-Reply-To: <1363775886.1390.90.camel@x61.thuisdomein>

Hi Paul,

On 20/03/13 20:38, Paul Bolle wrote:
> Kconfig symbol ROMVECSIZE is unused since commit
> f84f52a5c15db7d14a534815f27253b001735183 ("m68knommu: clean up linker
> script"). Let's clean up its Kconfig entry too.
>
> Signed-off-by: Paul Bolle <pebolle@tiscali.nl>

Thanks, I'll add it to the m68knommu git tree.

Regards
Greg


> ---
> Untested.
>
>   arch/m68k/Kconfig.machine | 9 ---------
>   1 file changed, 9 deletions(-)
>
> diff --git a/arch/m68k/Kconfig.machine b/arch/m68k/Kconfig.machine
> index 7240584..28ec0c0 100644
> --- a/arch/m68k/Kconfig.machine
> +++ b/arch/m68k/Kconfig.machine
> @@ -539,15 +539,6 @@ config ROMVEC
>   	  68000 type variants the vectors are at the base of the boot device
>   	  on system startup.
>
> -config ROMVECSIZE
> -	hex "Size of ROM vector region (in bytes)"
> -	default "0x400"
> -	depends on ROM
> -	help
> -	  Define the size of the vector region in ROM. For most 68000
> -	  variants this would be 0x400 bytes in size. Set to 0 if you do
> -	  not want a vector region at the start of the ROM.
> -
>   config ROMSTART
>   	hex "Address of the base of system image in ROM"
>   	default "0x400"
>


  reply	other threads:[~2013-03-21  5:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-20 10:38 [PATCH] m68k: clean up unused "config ROMVECSIZE" Paul Bolle
2013-03-21  5:33 ` Greg Ungerer [this message]
2013-03-21  5:33 ` Greg Ungerer
  -- strict thread matches above, loose matches on Subject: below --
2013-03-20 10:38 Paul Bolle

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=514A9BC7.2010201@uclinux.org \
    --to=gerg@uclinux.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.