linux-kernel - Re: [RFC PATCH 5/5] kernel/rcu/rcutorture.c:185 fix a sparse warning

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]

Message-ID: <CAJhHMCAkpFh+cpQA1R6Ar41K7GHgPKMMCs9DAqxMu0vJvHw3EA@mail.gmail.com>
Date:	Tue, 8 Jul 2014 18:46:50 -0400
From:	Pranith Kumar <bobby.prani@...il.com>
To:	Paul McKenney <paulmck@...ux.vnet.ibm.com>
Cc:	Josh Triplett <josh@...htriplett.org>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH 5/5] kernel/rcu/rcutorture.c:185 fix a sparse warning

On Tue, Jul 8, 2014 at 6:35 PM, Paul E. McKenney
<paulmck@...ux.vnet.ibm.com> wrote:
> On Wed, Jun 11, 2014 at 02:47:52PM -0700, josh@...htriplett.org wrote:
>> On Wed, Jun 11, 2014 at 04:39:43PM -0400, Pranith Kumar wrote:
>> > fix the following sparse warning
>> >
>> > kernel/rcu/rcutorture.c:185:1: warning: symbol 'boost_mutex' was not declared. Should it be static?
>> >
>> > by marking boost_mutex as a static mutex
>> >
>> > Signed-off-by: Pranith Kumar <bobby.prani@...il.com>
>>
>> Please preserve the comment alignment (by deleting a tab).  With that
>> fixed:
>> Reviewed-by: Josh Triplett <josh@...htriplett.org>
>
> Queued for 3.18.
>
> But Pranith, next time Josh gives you a review comment, could you please
> respond with the appropriate update?
>

I was away from my work desktop for the past few days. I actually sent
a fixed patch 10 min ago, but in a new series.

Sorry for missing this, I will drop an update promptly next time.


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