linux-kernel - Re: [PATCH] semaphore: fix comment

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, 5 Apr 2012 17:16:24 -0700 (PDT)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Daniel Baluta <daniel.baluta@...il.com>
Cc:	Lucia Rosculete <luciarosculete@...il.com>,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] semaphore: fix comment

On Tue, 13 Mar 2012, Daniel Baluta wrote:

> On Sat, Mar 3, 2012 at 4:18 PM, Lucia Rosculete
> <luciarosculete@...il.com> wrote:
> >         Replace "mutex" with "semaphore" in down_trylock comment
> >
> > Signed-off-by: Lucia Rosculete <luciarosculete@...il.com>
> > ---
> >  kernel/semaphore.c |    2 +-
> >  1 files changed, 1 insertions(+), 1 deletions(-)
> >
> > diff --git a/kernel/semaphore.c b/kernel/semaphore.c
> > index 60636a4..4567fc0 100644
> > --- a/kernel/semaphore.c
> > +++ b/kernel/semaphore.c
> > @@ -118,7 +118,7 @@ EXPORT_SYMBOL(down_killable);
> >  * down_trylock - try to acquire the semaphore, without waiting
> >  * @sem: the semaphore to be acquired
> >  *
> > - * Try to acquire the semaphore atomically.  Returns 0 if the mutex has
> > + * Try to acquire the semaphore atomically.  Returns 0 if the semaphore has
> >  * been acquired successfully or 1 if it it cannot be acquired.
> >  *
> >  * NOTE: This return value is inverted from both spin_trylock and
> 
> Hello Jiri,
> 
> Can you have a look?

Applied, thanks.

-- 
Jiri Kosina
SUSE Labs
--
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/