From: Zhu Yi <yi.zhu@intel.com>
To: Jiri Benc <jbenc@suse.cz>
Cc: netdev@vger.kernel.org, "John W. Linville" <linville@tuxdriver.com>
Subject: Re: [PATCH 6/6] d80211: add sysfs interface for QoS functions
Date: Fri, 15 Dec 2006 11:27:43 +0800 [thread overview]
Message-ID: <1166153263.2929.98.camel@debian.sh.intel.com> (raw)
In-Reply-To: <20061214122339.37fc6b6d@griffin.suse.cz>
On Thu, 2006-12-14 at 12:23 +0100, Jiri Benc wrote:
> So... what about implementing that into cfg80211? :-)
>
> I'm not inclined towards this patch (even if you address Stephen's
> comment).
OK. This is only for my testing (or maybe someone else wants to try the
code). I'm not asking to merge it. When all the other code is reviewed
and accepted, I will write a cfg80211 interface for it.
Thanks,
-yi
next prev parent reply other threads:[~2006-12-15 3:30 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 4:03 [PATCH 6/6] d80211: add sysfs interface for QoS functions Zhu Yi
2006-12-14 4:43 ` Stephen Hemminger
2006-12-14 11:23 ` Jiri Benc
2006-12-14 15:04 ` Johannes Berg
2006-12-15 3:27 ` Zhu Yi [this message]
2006-12-15 5:35 ` Simon Barber
2006-12-18 9:18 ` 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=1166153263.2929.98.camel@debian.sh.intel.com \
--to=yi.zhu@intel.com \
--cc=jbenc@suse.cz \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
/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).