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]
Date:	Fri, 4 Jan 2013 10:33:54 -0800
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	Cody P Schafer <cody@...ux.vnet.ibm.com>
Cc:	Dipankar Sarma <dipankar@...ibm.com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] rcu: comment: correct 'optimized' to 'optimize'.

On Fri, Jan 04, 2013 at 12:59:40PM -0500, Cody P Schafer wrote:
> Small gramar fix in rcutree comment regarding 'rcu_scheduler_active'
> var.

Queued, thank you!  I could not resist fixing a small nit in the commit
log as well.  ;-)

							Thanx, Paul

> ---
>  kernel/rcutree.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/kernel/rcutree.c b/kernel/rcutree.c
> index e441b77..bfb8972 100644
> --- a/kernel/rcutree.c
> +++ b/kernel/rcutree.c
> @@ -105,7 +105,7 @@ int rcu_num_nodes __read_mostly = NUM_RCU_NODES; /* Total # rcu_nodes in use. */
>   * The rcu_scheduler_active variable transitions from zero to one just
>   * before the first task is spawned.  So when this variable is zero, RCU
>   * can assume that there is but one task, allowing RCU to (for example)
> - * optimized synchronize_sched() to a simple barrier().  When this variable
> + * optimize synchronize_sched() to a simple barrier().  When this variable
>   * is one, RCU must actually do all the hard work required to detect real
>   * grace periods.  This variable is also used to suppress boot-time false
>   * positives from lockdep-RCU error checking.
> -- 
> 1.8.0.3
> 

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ