linux-kernel - Re: [Doc] class_find_device: fix reference to argument

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

Date:	Sun, 21 Aug 2011 14:53:55 -0700
From:	Randy Dunlap <rdunlap@...otime.net>
To:	Wanlong Gao <wanlong.gao@...il.com>
Cc:	linux-kernel@...r.kernel.org, gregkh <greg@...ah.com>
Subject: Re: [Doc] class_find_device: fix reference to argument

On Sun, 21 Aug 2011 14:46:04 +0000 (UTC) Wanlong Gao wrote:

> Rolf Eike Beer <eike <at> sf-mail.de> writes:
> 
> > 
> > Signed-off-by: Rolf Eike Beer <eike-kernel <at> sf-tec.de>
> > ---
> >  drivers/base/class.c |    2 +-
> >  1 files changed, 1 insertions(+), 1 deletions(-)
> > 
> 
> > - * @fn is allowed to do anything including calling back into class
> > + * @match is allowed to do anything including calling back into class
> >   * code.  There's no locking restriction.
> >   */
> >  struct device *class_find_device(struct class *class, struct device *start,
> 
> NACK, it means the function class_find_device but not the @match.

Are you sure?  Looks to me like a comment that was copied from
class_for_each_device() but shouldn't have been copied.

Anyway, I'll cc: Greg to see if he knows.

---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
--
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/