All of lore.kernel.org
 help / color / mirror / Atom feed
From: Inaky Perez-Gonzalez <inaky@linux.intel.com>
To: wimax@linuxwimax.org, netdev@vger.kernel.org
Cc: Inaky Perez-Gonzalez <inaky@linux.intel.com>,
	Randy Dunlap <randy.dunlap@oracle.com>
Subject: [PATCH] wimax: fix kernel-doc for debufs_dentry member of struct wimax_dev [v2]
Date: Thu,  8 Jan 2009 12:59:56 -0800	[thread overview]
Message-ID: <1231448396-8582-1-git-send-email-inaky@linux.intel.com> (raw)
In-Reply-To: <1231447827-7999-1-git-send-email-inaky@linux.intel.com>

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@linux.intel.com>
Cc: Randy Dunlap <randy.dunlap@oracle.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.
+ *
  * Description:
  * This structure defines a common interface to access all WiMAX
  * devices from different vendors and provides a common API as well as
-- 
1.5.6.5


  parent reply	other threads:[~2009-01-08 20:59 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-08 20:50 [PATCH] wimax: fix kernel-doc for debufs_dentry member of struct wimax_dev Inaky Perez-Gonzalez
2009-01-08 20:57 ` David Miller
2009-01-08 21:02   ` Inaky Perez-Gonzalez
2009-01-08 20:59 ` Inaky Perez-Gonzalez [this message]
2009-01-09  5:36   ` [PATCH] wimax: fix kernel-doc for debufs_dentry member of struct wimax_dev [v2] Randy Dunlap
2009-01-09  7:23     ` Inaky Perez-Gonzalez
2009-01-09  8:41       ` [PATCH] wimax: fix typo in kernel-doc for debugfs_dentry in struct wimax_dev Inaky Perez-Gonzalez
2009-01-09 17:34     ` Inaky Perez-Gonzalez
2009-01-10  7:09       ` David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1231448396-8582-1-git-send-email-inaky@linux.intel.com \
    --to=inaky@linux.intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=wimax@linuxwimax.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.