From: "Malinen, Jouni" <jouni@qca.qualcomm.com>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
"Kushwaha, Purushottam" <pkushwah@qti.qualcomm.com>
Subject: Re: [PATCH 3/3] cfg80211: Specify the reason for connect timeout
Date: Thu, 12 Jan 2017 15:03:34 +0000 [thread overview]
Message-ID: <20170112150332.GA19935@jouni.qca.qualcomm.com> (raw)
In-Reply-To: <1484231540.5391.6.camel@sipsolutions.net>
On Thu, Jan 12, 2017 at 03:32:20PM +0100, Johannes Berg wrote:
>=20
> > We don't.. This discussion here is about the C API where we cannot
> > remove the argument from the call without adding yet another inline
> > wrapper, but the actual function that generates the netlink message
> > does not add the timeout reason attribute for success or explicit
> > rejection cases.
>=20
> Ah. But we can just say here then that it's ignored in those cases, and
> not really worry about it?
Sure, I'll update the comment to say that.
--=20
Jouni Malinen PGP id EFC895FA=
next prev parent reply other threads:[~2017-01-12 15:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 17:53 [PATCH v3 1/3] cfg80211: Add support to sched scan to report better BSSs Jouni Malinen
2017-01-09 17:53 ` [PATCH v2 2/3] cfg80211: Add support to randomize TA of Public Action frames Jouni Malinen
2017-01-11 13:25 ` Johannes Berg
2017-01-09 17:53 ` [PATCH 3/3] cfg80211: Specify the reason for connect timeout Jouni Malinen
2017-01-09 20:24 ` Arend Van Spriel
2017-01-11 13:13 ` Malinen, Jouni
2017-01-11 13:26 ` Johannes Berg
2017-01-12 14:01 ` Malinen, Jouni
2017-01-11 13:31 ` Johannes Berg
2017-01-12 13:58 ` Malinen, Jouni
2017-01-12 14:06 ` Johannes Berg
2017-01-12 14:29 ` Malinen, Jouni
2017-01-12 14:32 ` Johannes Berg
2017-01-12 15:03 ` Malinen, Jouni [this message]
2017-01-09 20:07 ` [PATCH v3 1/3] cfg80211: Add support to sched scan to report better BSSs Arend Van Spriel
2017-01-11 7:48 ` Vamsi, Krishna
2017-01-11 13:22 ` Johannes Berg
2017-01-12 13:50 ` Vamsi, Krishna
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=20170112150332.GA19935@jouni.qca.qualcomm.com \
--to=jouni@qca.qualcomm.com \
--cc=johannes@sipsolutions.net \
--cc=linux-wireless@vger.kernel.org \
--cc=pkushwah@qti.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 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.