linux-kernel - Re: [PATCH] m68k: clean up unused "config ROMVECSIZE"

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Thu, 21 Mar 2013 15:33:59 +1000
From:	Greg Ungerer <gerg@...inux.org>
To:	Paul Bolle <pebolle@...cali.nl>
CC:	Geert Uytterhoeven <geert@...ux-m68k.org>,
	linux-m68k@...ts.linux-m68k.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] m68k: clean up unused "config ROMVECSIZE"

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@...cali.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"
>

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/