linux-kernel - Re: [PATCH] [TRIVIAL] hvcs: fix typo in 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]

Message-ID: <alpine.LNX.2.00.1102151024550.2160@pobox.suse.cz>
Date:	Tue, 15 Feb 2011 10:25:03 +0100 (CET)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Jesper Juhl <jj@...osbits.net>
Cc:	Paul Bolle <pebolle@...cali.nl>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] [TRIVIAL] hvcs: fix typo in comment

On Tue, 15 Feb 2011, Jesper Juhl wrote:

> On Tue, 15 Feb 2011, Paul Bolle wrote:
> 
> > Signed-off-by: Paul Bolle <pebolle@...cali.nl>
> > ---
> >  drivers/char/hvcs.c |    2 +-
> >  1 files changed, 1 insertions(+), 1 deletions(-)
> > 
> > diff --git a/drivers/tty/hvc/hvcs.c b/drivers/tty/hvc/hvcs.c
> > index bedc6c1..af4e650 100644
> > --- a/drivers/tty/hvc/hvcs.c
> > +++ b/drivers/tty/hvc/hvcs.c
> > @@ -292,7 +292,7 @@ struct hvcs_struct {
> >  	/*
> >  	 * Any variable below the kref is valid before a tty is connected and
> >  	 * stays valid after the tty is disconnected.  These shouldn't be
> > -	 * whacked until the koject refcount reaches zero though some entries
> > +	 * whacked until the kobject refcount reaches zero though some entries
> >  	 * may be changed via sysfs initiatives.
> >  	 */
> >  	struct kref kref; /* ref count & hvcs_struct lifetime */
> > 
> 
> Reviewed-by: Jesper Juhl <jj@...osbits.net>

Applied, thanks.

-- 
Jiri Kosina
SUSE Labs, Novell Inc.
--
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/