linux-kernel - Re: [PATCH 0/9] rcu: trivial sparse and return type fixes for rcu

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

Message-ID: <CAJhHMCDUy_=LZWkhA5OU3WsfpyFwxwDJGT6rnqY3E6t=ZXQk3g@mail.gmail.com>
Date:	Tue, 8 Jul 2014 18:32:03 -0400
From:	Pranith Kumar <bobby.prani@...il.com>
To:	LKML <linux-kernel@...r.kernel.org>,
	Paul McKenney <paulmck@...ux.vnet.ibm.com>,
	Josh Triplett <josh@...htriplett.org>
Subject: Re: [PATCH 0/9] rcu: trivial sparse and return type fixes for rcu

This patch series contains trivial fixes for sparse warnings and using bool
types where appropriate instead of 0/1.

I can probably merge the return type changes into one commit if you think that
is appropriate.

Pranith Kumar (9):
  rcu: fix sparse warning about rcu_batches_completed_preempt(
) being
    non-static
  rcu: use bool type for return value in rcu_is_watching()
  rcu: Fix a sparse warning about boost_mutex being non-static
  rcu: return bool type in rcu_lockdep_current_cpu_online()
  rcu: return bool type for rcu_try_advance_all_cbs()
  rcu: use true/false for return in __call_rcu_nocb()
  rcu: use true/false for return in rcu_nocb_adopt_orphan_cbs()
  rcu: use false for return in __call_rcu_nocb()
  rcu: use bool return type in rcu_nocb_adopt_orphan_cbs()

 include/linux/rcupdate.h |  2 +-
 kernel/rcu/rcutorture.c  |  2 +-
 kernel/rcu/tree.c        |  2 +-
 kernel/rcu/tree_plugin.h | 16 ++++++++--------
 4 files changed, 11 insertions(+), 11 deletions(-)
--
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/