From: Kalle Valo <kvalo@qca.qualcomm.com>
To: David Miller <davem@davemloft.net>
Cc: <linville@tuxdriver.com>, <linux-wireless@vger.kernel.org>,
<netdev@vger.kernel.org>
Subject: Re: pull request: wireless-next 2011-11-28
Date: Tue, 29 Nov 2011 13:58:06 +0200 [thread overview]
Message-ID: <4ED4C8CE.8030408@qca.qualcomm.com> (raw)
In-Reply-To: <20111128.195516.37800643865997337.davem@davemloft.net>
On 11/29/2011 02:55 AM, David Miller wrote:
> Pulled, but please push back on the ath6kl guys, they seem to have
> this disease where they add tons of debugfs files
Sorry about that. I was under impression that there are no strict rules
for debugfs files and drivers can add them without too much worries, but
it seems I was wrong.
> for controlling things like QoS from userspace instead of creating
> and using generic configuration machanisms via netlink or similar
> that any other driver could support too.
Adding a generic QoS interface would take some time to implement and I
doubt that we (=ath6kl team) can do that anytime soon as our first
challange has been to get ath6kl working properly with cfg80211. That's
why we ended up having a debugfs interface for qos as our first step.
Kalle
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo-A+ZNKFmMK5xy9aJCnZT0Uw@public.gmane.org>
To: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
Cc: <linville-2XuSBdqkA4R54TAoqtyWWQ@public.gmane.org>,
<linux-wireless-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
<netdev-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: pull request: wireless-next 2011-11-28
Date: Tue, 29 Nov 2011 13:58:06 +0200 [thread overview]
Message-ID: <4ED4C8CE.8030408@qca.qualcomm.com> (raw)
In-Reply-To: <20111128.195516.37800643865997337.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
On 11/29/2011 02:55 AM, David Miller wrote:
> Pulled, but please push back on the ath6kl guys, they seem to have
> this disease where they add tons of debugfs files
Sorry about that. I was under impression that there are no strict rules
for debugfs files and drivers can add them without too much worries, but
it seems I was wrong.
> for controlling things like QoS from userspace instead of creating
> and using generic configuration machanisms via netlink or similar
> that any other driver could support too.
Adding a generic QoS interface would take some time to implement and I
doubt that we (=ath6kl team) can do that anytime soon as our first
challange has been to get ath6kl working properly with cfg80211. That's
why we ended up having a debugfs interface for qos as our first step.
Kalle
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2011-11-29 12:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-28 20:02 pull request: wireless-next 2011-11-28 John W. Linville
2011-11-28 20:02 ` John W. Linville
2011-11-29 0:55 ` David Miller
2011-11-29 0:55 ` David Miller
2011-11-29 11:58 ` Kalle Valo [this message]
2011-11-29 11:58 ` Kalle Valo
2011-11-29 8:22 ` Johannes Berg
2011-11-29 8:22 ` Johannes Berg
2011-11-29 13:42 ` John W. Linville
2011-11-29 13:42 ` John W. Linville
2011-11-29 13:54 ` 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=4ED4C8CE.8030408@qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=davem@davemloft.net \
--cc=linux-wireless@vger.kernel.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.