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[6]: cfg80211 and rfkill_backport question.
Date: Wed, 16 Sep 2009 12:14:43 +0300 [thread overview]
Message-ID: <1382256815.20090916121443@mail.ru> (raw)
In-Reply-To: <43e72e890909151817u375cd847r7cdf78b53f26fe2f@mail.gmail.com>
Hello Luis!
Wednesday, September 16, 2009, 4:17:40 AM, Luis R. Rodriguez wrote:
> They don't have to be exported and inlined, its one or the other. So
Yes, that's what I supposed.
> just ensure you your symbols you have conflicts with as
> EXPORT_SYMBOL() or defined in a header file as inline. You will
> obviously also need the header declaration if defined as an
> EXPORT_SYMBOL.
>From what I checked it all looks fine to me, except that there is
a circular dependency between cfg80211 and rfkill_backport (which
is confirmed by nm output I suppose). Is this circular dependency
intentional? Or, could it be avoided? (My understanding was that
as module loader loads one file at a time, it just have no way
to resolve such symbols, maybe I'm wrong on this)
Nikolai
> Luis
next prev parent reply other threads:[~2009-09-16 8:07 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 ` Re[4]: " Nikolai ZHUBR
2009-09-16 1:17 ` Luis R. Rodriguez
2009-09-16 9:14 ` Nikolai ZHUBR [this message]
2009-09-16 15:24 ` Re[6]: " 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=1382256815.20090916121443@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).