From: Zhu Yi <yi.zhu@intel.com>
To: Jiri Benc <jbenc@suse.cz>
Cc: linux-wireless@vger.kernel.org,
"John W. Linville" <linville@tuxdriver.com>,
Michael Wu <flamingice@sourmilk.net>
Subject: Re: [PATCH 3/3] mac80211: debugfs support for TSM and DLS
Date: Fri, 08 Jun 2007 09:17:55 +0800 [thread overview]
Message-ID: <1181265476.3039.86.camel@debian.sh.intel.com> (raw)
In-Reply-To: <20070607223934.4726e8a7@griffin.suse.cz>
On Thu, 2007-06-07 at 22:39 +0200, Jiri Benc wrote:
> A global variable? Common for all devices you have in your computer?
> That's broken.
OK, it can be fixed. But it is that broken if you treat it as a debug
helper and don't use it on mulitple interfaces simultaneously.
> > +
> > +#define DEBUGFS_QOS_FILE(name, f) \
> > +static ssize_t qos_ ##name## _write(struct file *file, \
> > + const char __user *userbuf, \
> > + size_t count, loff_t *ppos) \
> > +{ \
> > + struct ieee80211_sub_if_data *sdata = file->private_data; \
> > + \
> > + f(sdata->dev, &sdata->u.sta, &_tspec); \
> > + \
> > + return count; \
> > +} \
>
> Triggering an event just by writing anything to the debugfs file
> doesn't seem like a clean and intelligible way to configure things.
>
> Also, are you aware this is just a _debug_ stuff? Given the fact that
> you're calling (for example) ieee80211_send_addts from debugfs handler
> only, it looks like you're misusing it as an user space API.
If you follow the thread, I will write a user space API with cfg80211.
This one for debugging only.
-yi
next prev parent reply other threads:[~2007-06-08 1:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-06 8:22 [PATCH 3/3] mac80211: debugfs support for TSM and DLS Zhu Yi
2007-06-07 20:39 ` Jiri Benc
2007-06-08 1:17 ` Zhu Yi [this message]
2007-06-08 9:59 ` Jiri Benc
-- strict thread matches above, loose matches on Subject: below --
2007-05-25 11:52 Zhu Yi
2007-05-25 16:20 ` Randy Dunlap
2007-05-25 16:26 ` Michael Buesch
2007-05-28 1:43 ` Zhu Yi
2007-05-14 5:15 Zhu Yi
2007-05-24 7:12 ` Michael Wu
2007-05-24 7:51 ` Zhu Yi
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=1181265476.3039.86.camel@debian.sh.intel.com \
--to=yi.zhu@intel.com \
--cc=flamingice@sourmilk.net \
--cc=jbenc@suse.cz \
--cc=linux-wireless@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 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).