linux-kernel - Re: [-mm patch] kernel/printk.c: make 2 variables static

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] [thread-next>] [day] [month] [year] [list]

Message-Id: <20070729095151.f5f96c99.rdunlap@xenotime.net>
Date:	Sun, 29 Jul 2007 09:51:51 -0700
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Adrian Bunk <bunk@...sta.de>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [-mm patch] kernel/printk.c: make 2 variables static

On Sun, 29 Jul 2007 16:59:18 +0200 Adrian Bunk wrote:

> On Wed, Jul 25, 2007 at 04:03:04AM -0700, Andrew Morton wrote:
> >...
> > Changes since 2.6.22-rc6-mm1:
> >...
> > +slow-down-printk-during-boot.patch
> >...
> >  Misc
> >...
> 
> This patch makes two needlessly global variables static.
> 
> Signed-off-by: Adrian Bunk <bunk@...sta.de>

Aye.  Thanks.

> ---
> --- linux-2.6.23-rc1-mm1/kernel/printk.c.old	2007-07-26 22:40:09.000000000 +0200
> +++ linux-2.6.23-rc1-mm1/kernel/printk.c	2007-07-26 22:40:50.000000000 +0200
> @@ -166,8 +166,8 @@
>  
>  #ifdef CONFIG_BOOT_PRINTK_DELAY
>  
> -unsigned int boot_delay; /* msecs delay after each printk during bootup */
> -unsigned long long printk_delay_msec; /* per msec, based on boot_delay */
> +static unsigned int boot_delay; /* msecs delay after each printk during bootup */
> +static unsigned long long printk_delay_msec; /* per msec, based on boot_delay */
>  
>  static int __init boot_delay_setup(char *str)
>  {


---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
-
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/