netdev - Re: [PATCH][RFC] Infrastructure for out-of-band parameter passing

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 for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20100608183616.GB31503@dvomlehn-lnx2.corp.sa.net>
Date:	Tue, 8 Jun 2010 11:36:16 -0700
From:	David VomLehn <dvomlehn@...co.com>
To:	Randy Dunlap <rdunlap@...otime.net>
Cc:	to@...mlehn-lnx2.corp.sa.net, netdev@...r.kernel.org
Subject: Re: [PATCH][RFC] Infrastructure for out-of-band parameter passing

On Tue, Jun 08, 2010 at 10:31:20AM -0500, Randy Dunlap wrote:
> On Mon, 7 Jun 2010 17:30:49 -0700 David VomLehn wrote:
> 
> > Infrastructure to support out of band/indirect passing of data to functions.
...
> > +/**
> > + * oobparam_push - push an out of band parameter frame on the OOB param stack
> > + * @head	Pointer to the OOB parameter stack top, which must be in the
> > + *		task structure.
> > + * @frame	Pointer to the OOB parameter frame, generally embedded in
> > + *		another structure
> 
> Need a colon ':' after the parameter names for kernel-doc notation:

That's what I get for relying on memory...thanks!
...
> ---
> ~Randy
> *** Remember to use Documentation/SubmitChecklist when testing your code ***

-- 
David VL
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html