linux-kernel - Re: [PATCH] TRIVIAL: fix grammo in bus_for_each

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, 14 May 2009 23:15:38 +0200 (CEST)
From:	Jiri Kosina <jkosina@...e.cz>
To:	Randy Dunlap <randy.dunlap@...cle.com>
Cc:	Alex Chiang <achiang@...com>, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] TRIVIAL: fix grammo in bus_for_each_dev() kerneldoc

On Thu, 14 May 2009, Randy Dunlap wrote:

> Alex Chiang wrote:
> > Cc: Randy Dunlap <randy.dunlap@...cle.com>
> 
> Acked-by: Randy Dunlap <randy.dunlap@...cle.com>
> 
> Thanks.
> 
> > Signed-off-by: Alex Chiang <achiang@...com>
> > ---
> > 
> >  drivers/base/bus.c |    2 +-
> >  1 files changed, 1 insertions(+), 1 deletions(-)
> > 
> > diff --git a/drivers/base/bus.c b/drivers/base/bus.c
> > index dc030f1..4476a4e 100644
> > --- a/drivers/base/bus.c
> > +++ b/drivers/base/bus.c
> > @@ -279,7 +279,7 @@ static struct device *next_device(struct klist_iter *i)
> >   *
> >   * NOTE: The device that returns a non-zero value is not retained
> >   * in any way, nor is its refcount incremented. If the caller needs
> > - * to retain this data, it should do, and increment the reference
> > + * to retain this data, it should do so, and increment the reference
> >   * count in the supplied callback.
> >   */
> >  int bus_for_each_dev(struct bus_type *bus, struct device *start,

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/