From: Johannes Berg <johannes@sipsolutions.net>
To: Frank Schneider <twodipu@hotmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: Loop detected - calling function from different modules
Date: Thu, 31 Aug 2006 11:57:46 +0200 [thread overview]
Message-ID: <1157018266.3065.17.camel@ux156> (raw)
In-Reply-To: <BAY101-F33A13C37EC4876E17B74C0AB3F0@phx.gbl>
Frank,
> Any suggestions to do that please ?
d80211 has a hardware definition struct that is registered by the driver
and contains a callback that is called for each frame. This is the
direction you should take as well:
hard_start_xmit (generic code)
calls
hardware_xmit (your module code, e.g. in a struct wlan_device)
johannes
next prev parent reply other threads:[~2006-08-31 9:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-30 20:58 Loop detected - calling function from different modules Frank Schneider
2006-08-30 21:26 ` Stephen Hemminger
2006-09-03 9:02 ` Frank Schneider
2006-08-31 7:17 ` Johannes Berg
2006-08-31 9:53 ` Frank Schneider
2006-08-31 9:57 ` Johannes Berg [this message]
2006-08-31 11:10 ` Frank Schneider
2006-09-03 11:20 ` Frank Schneider
2006-09-04 7:07 ` Johannes Berg
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=1157018266.3065.17.camel@ux156 \
--to=johannes@sipsolutions.net \
--cc=netdev@vger.kernel.org \
--cc=twodipu@hotmail.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).