linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: "Malinen, Jouni" <jouni@qca.qualcomm.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"Xu, Peng" <pxu@qca.qualcomm.com>
Subject: Re: [PATCH] cfg80211: Add HT and VHT information in start_ap
Date: Mon, 12 Sep 2016 12:09:42 +0200	[thread overview]
Message-ID: <1473674982.29016.10.camel@sipsolutions.net> (raw)
In-Reply-To: <1472198948.390.20.camel@sipsolutions.net> (sfid-20160826_100916_928008_E35799B6)

So I haven't seen a response from you guys:

I have no major objections to this. However, a few things:

1) are you planning to add support for this into a kernel driver at
   all, anyway?
2) are you planning to have a driver upstream that contains the now
   necessary parsing?

Depending on the answers, I suppose we could/should merge this:

no  *  : don't merge
yes no : merge
yes yes: don't merge, put parsing into cfg80211

I guess?

We don't have to always draw a too rigid line for non-upstream things, but it's still disappointing that you keep proposing things that are only used for non-upstream drivers.

johannes

  reply	other threads:[~2016-09-12 10:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-15 18:07 [PATCH] cfg80211: Add HT and VHT information in start_ap Jouni Malinen
2016-08-16  6:52 ` Johannes Berg
2016-08-16 12:34   ` Malinen, Jouni
2016-08-26  8:09     ` Johannes Berg
2016-09-12 10:09       ` Johannes Berg [this message]
2016-10-03 21:15         ` Malinen, Jouni
2016-10-04 13:25           ` Johannes Berg
2016-10-04 16:15             ` Malinen, Jouni
2016-10-13 13:12               ` 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=1473674982.29016.10.camel@sipsolutions.net \
    --to=johannes@sipsolutions.net \
    --cc=jouni@qca.qualcomm.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=pxu@qca.qualcomm.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).