linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikolai ZHUBR <zhubr@mail.ru>
To: "Luis R. Rodriguez" <mcgrof@gmail.com>
Cc: linux-wireless@vger.kernel.org,
	Gaurav Jauhar <gaurav.jauhar@atheros.com>,
	Senthil Balasubramanian <senthilkumar@atheros.com>
Subject: Re[4]: cfg80211 and rfkill_backport question.
Date: Wed, 16 Sep 2009 05:02:13 +0300	[thread overview]
Message-ID: <90263558.20090916050213@mail.ru> (raw)
In-Reply-To: <43e72e890909151649x66321b6emdc2977473e22872a@mail.gmail.com>

Wednesday, September 16, 2009, 2:49:04 AM, Luis R. Rodriguez wrote:
> Check if the symbols you had issues with were indeed exported via
> EXPORT_SYMBOL() on the compat code (compat/*.c) or if whether they
> were defined via a header as an inline (compat/*.h).
As far as I can see, the symbols in question are not defined as inline:

compat/compat-2.6.26.c:
  EXPORT_SYMBOL_GPL(dev_set_name);
  
compat/compat-2.6.26.h:
  extern int dev_set_name(struct device *dev, const char *name, ...)
                        __attribute__((format(printf, 2, 3)));
net/rfkill/core.c:
  EXPORT_SYMBOL(rfkill_blocked);

include/linux/rfkill-backport.h:
  #if defined(CONFIG_RFKILL_BACKPORT) || defined(CONFIG_RFKILL_MODULE_BACKPORT)
  .......
  bool rfkill_blocked(struct rfkill *rfkill);
  #else /* !RFKILL */
  .......
  static inline bool rfkill_blocked(struct rfkill *rfkill)
  {
        return false;
  }
  #endif /* RFKILL || RFKILL_MODULE */
  
config.mk:  
  ifdef CONFIG_COMPAT_WIRELESS_31
  CONFIG_RFKILL_BACKPORT=m
  ......

Maybe module loader is supposed to do some magic with symbols, which openwrt 
is missing? However, other modules work just as usual, there are no problems
with lib80211* for instance.

 Nikolai



  reply	other threads:[~2009-09-16  0:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-16  0:09 cfg80211 and rfkill_backport question Nikolai ZHUBR
2009-09-15 23:14 ` Luis R. Rodriguez
2009-09-16  0:46   ` Re[2]: " Nikolai ZHUBR
2009-09-15 23:49     ` Luis R. Rodriguez
2009-09-16  2:02       ` Nikolai ZHUBR [this message]
2009-09-16  1:17         ` Re[4]: " Luis R. Rodriguez
2009-09-16  9:14           ` Re[6]: " Nikolai ZHUBR
2009-09-16 15:24             ` Hin-Tak Leung
2009-09-16 22:11               ` Re[8]: " Nikolai ZHUBR
2009-09-16 11:12           ` Re[6]: " Nikolai ZHUBR

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=90263558.20090916050213@mail.ru \
    --to=zhubr@mail.ru \
    --cc=gaurav.jauhar@atheros.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=mcgrof@gmail.com \
    --cc=senthilkumar@atheros.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;
as well as URLs for NNTP newsgroup(s).