From: Randy Dunlap <rdunlap@xenotime.net>
To: lkml <linux-kernel@vger.kernel.org>
Cc: linux-wimax@intel.com
Cc: wimax@linuxwimax.org
Cc: rdunlap@xenotime.net
Subject: [PATCH 1/1] wimax: delete struct wimax_dev field rfkill_input
Date: Sun, 10 Jul 2011 19:21:28 -0700 [thread overview]
Message-ID: <1310350888180@xenotime.net> (raw)
In-Reply-To:
From: Randy Dunlap <rdunlap@xenotime.net>
"make htmldocs" warns that struct member "rfkill_input" does not have
a description. After searching all kernel .[hc] files, this field
is not used, so remove it.
Warning(include/net/wimax.h:432): No description found for parameter 'rfkill_input'
Signed-off-by: Randy Dunlap <rdunlap@xenotime.net>
---
include/net/wimax.h | 1 -
1 file changed, 1 deletion(-)
--- linux-3.0-rc6-git6.orig/include/net/wimax.h
+++ linux-3.0-rc6-git6/include/net/wimax.h
@@ -423,7 +423,6 @@ struct wimax_dev {
int (*op_reset)(struct wimax_dev *wimax_dev);
struct rfkill *rfkill;
- struct input_dev *rfkill_input;
unsigned rf_hw;
unsigned rf_sw;
char name[32];
--
next reply other threads:[~2011-07-11 2:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-11 2:21 Randy Dunlap [this message]
2011-07-11 16:33 ` [PATCH 1/1] wimax: delete struct wimax_dev field rfkill_input Perez-Gonzalez, Inaky
2011-07-13 14:05 ` Vitaliy Ivanov
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=1310350888180@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wimax@intel.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox