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
| ||
|
Date: Mon, 22 Aug 2011 16:29:56 +0800 From: Wanlong Gao <wanlong.gao@...il.com> To: Randy Dunlap <rdunlap@...otime.net> Cc: linux-kernel@...r.kernel.org, gregkh <greg@...ah.com> Subject: Re: [Doc] class_find_device: fix reference to argument no,not sure. but i think you are right. Randy Dunlap <rdunlap@...otime.net> wrote: >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 ***
Powered by blists - more mailing lists