All of lore.kernel.org
 help / color / mirror / Atom feed
From: mike@mspradling.com
To: davem@davemloft.net, hugh.dickins@ticali.co.uk,
	linville@tuxdriver.com, johannes@sipsolutions.net,
	mike@mspradling.com, linux-kernel@vger.kernel.org
Subject: [PATCH] Fixed bug in Wireless Extension Code (CONFIG_WEXT_CORE).
Date: Sun, 22 Nov 2009 19:36:42 -0500	[thread overview]
Message-ID: <1258936602-6110-1-git-send-email-mike@mspradling.com> (raw)

From: Michael Spradling <mike@mspradling.com>

When CONFIG_WEXT_CORE is not enabled and CONFIG_WEXT_PRIV is enabled
there currently is a few build errors.  This is because several
functions call function call_commit_handler which is currently only
defined when CONFIG_WEXT_CORE is enabled.

Signed-off-by: Michael Spradling <mike@mspradling.com>
---
 include/net/wext.h |    4 ++++
 1 files changed, 4 insertions(+), 0 deletions(-)

diff --git a/include/net/wext.h b/include/net/wext.h
index 4f6e742..773c8c6 100644
--- a/include/net/wext.h
+++ b/include/net/wext.h
@@ -24,6 +24,10 @@ static inline int compat_wext_handle_ioctl(struct net *net, unsigned int cmd,
 {
 	return -EINVAL;
 }
+static inline int call_commit_handler(struct net_device *dev)
+{
+	return -EINVAL;
+}
 #endif
 
 #ifdef CONFIG_WEXT_PROC
-- 
1.6.5.2



             reply	other threads:[~2009-11-23  1:41 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-23  0:36 mike [this message]
2009-11-23  9:45 ` [PATCH] Fixed bug in Wireless Extension Code (CONFIG_WEXT_CORE) Johannes Berg
2009-11-23 15:42   ` Michael Spradling
2009-11-23 15:53     ` Johannes Berg
2009-11-24  1:12       ` Michael Spradling
2009-12-01 17:46         ` Randy Dunlap

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=1258936602-6110-1-git-send-email-mike@mspradling.com \
    --to=mike@mspradling.com \
    --cc=davem@davemloft.net \
    --cc=hugh.dickins@ticali.co.uk \
    --cc=johannes@sipsolutions.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linville@tuxdriver.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 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.