netdev - Re: [PATCH] wimax: fix kernel-doc for debufs_dentry member of struct wimax

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:	Thu, 08 Jan 2009 21:36:40 -0800
From:	Randy Dunlap <randy.dunlap@...cle.com>
To:	Inaky Perez-Gonzalez <inaky@...ux.intel.com>
CC:	wimax@...uxwimax.org, netdev@...r.kernel.org,
	Randy Dunlap <randy.dunlap@...cle.com>
Subject: Re: [PATCH] wimax: fix kernel-doc for debufs_dentry member of struct
 wimax_dev [v2]

Inaky Perez-Gonzalez wrote:
> Reported by Randy Dunlap from a warning in the v2.6.29 merge window
> tree as of 2009/1/8.
> 
> v2 fixes Randy Dunlap's email address.
> 
> Signed-off-by: Inaky Perez-Gonzalez <inaky@...ux.intel.com>
> Cc: Randy Dunlap <randy.dunlap@...cle.com>
> ---
>  include/net/wimax.h |    3 +++
>  1 files changed, 3 insertions(+), 0 deletions(-)
> 
> diff --git a/include/net/wimax.h b/include/net/wimax.h
> index 1602614..073809c 100644
> --- a/include/net/wimax.h
> +++ b/include/net/wimax.h
> @@ -323,6 +323,9 @@ struct input_dev;
>   *
>   * @rf_hw: [private] State of the hardware radio switch (OFF/ON)
>   *
> + * @debufs_dentry: [private] Used to hook up a debugfs entry. This
> + *     shows up in the debugfs root as wimax:DEVICENAME.

Inaky, this was supposed to be @debugfs_dentry.  (typo)

> + *
>   * Description:
>   * This structure defines a common interface to access all WiMAX
>   * devices from different vendors and provides a common API as well as


-- 
~Randy
--
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