From: Johannes Berg <johannes@sipsolutions.net>
To: Ben Greear <greearb@candelatech.com>
Cc: linux-wireless@vger.kernel.org
Subject: Re: [PATCH v6 1/2] wireless: Support ht-capabilities over-rides.
Date: Tue, 08 Nov 2011 19:21:14 +0100 [thread overview]
Message-ID: <1320776474.24797.32.camel@jlt3.sipsolutions.net> (raw)
In-Reply-To: <4EB9720B.8080704@candelatech.com>
On Tue, 2011-11-08 at 10:16 -0800, Ben Greear wrote:
> > Fair enough. I think what I'm really after is having a way to know wtf
> > we're using when you requested something. That would probably be more
> > useful overall.
ok.
> The current ht_cap settings for each station are in debugfs, so hopefully it
> would not be that difficult to add it to a netlink response. Perhaps
> it's already there..I haven't looked yet.
>
> > FWIW, I did talk to some people at the kernel summit about the -EINVAL
> > thing and maybe there's an idea to send back the invalid attribute at
> > least, but doesn't really matter here. I'm OK with just allowing it all
> > since it's not going to be used a lot anyway.
>
> Ok, I'll add some printks.
I really don't think you should add printks here for this.
> > OTOH, if you request a connect(), you don't even know the band and
> > technically a driver could have different capabilities on different
> > bands.
>
> Lets see if any other drivers try to support these features. Anyone
> doing that work will likely see some ways to make use of common code
> and things can be shuffled then. As written, the patches are not overly
> invasive, so I think we can move stuff around later without too much
> trouble.
Ok, fair enough.
johannes
prev parent reply other threads:[~2011-11-08 18:21 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-07 23:14 [PATCH v6 1/2] wireless: Support ht-capabilities over-rides greearb
2011-11-07 23:14 ` [PATCH v6 2/2] mac80211: Support ht-cap over-rides greearb
2011-11-08 8:14 ` [PATCH v6 1/2] wireless: Support ht-capabilities over-rides Johannes Berg
2011-11-08 17:43 ` Ben Greear
2011-11-08 18:00 ` Johannes Berg
2011-11-08 18:16 ` Ben Greear
2011-11-08 18:21 ` Johannes Berg [this message]
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=1320776474.24797.32.camel@jlt3.sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=greearb@candelatech.com \
--cc=linux-wireless@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