From: Johannes Berg <johannes@sipsolutions.net>
To: Jouni Malinen <jouni@qca.qualcomm.com>
Cc: linux-wireless@vger.kernel.org,
Vidyullatha Kanchanapally <vkanchan@qti.qualcomm.com>
Subject: Re: [PATCH 1/2] cfg80211: Use a structure to pass connect response params
Date: Fri, 31 Mar 2017 08:32:01 +0200 [thread overview]
Message-ID: <1490941921.24283.2.camel@sipsolutions.net> (raw)
In-Reply-To: <1490908954-5412-1-git-send-email-jouni@qca.qualcomm.com>
On Fri, 2017-03-31 at 00:22 +0300, Jouni Malinen wrote:
> From: Vidyullatha Kanchanapally <vkanchan@qti.qualcomm.com>
>
> Currently the connect event from driver takes all the connection
> response parameters as arguments. With support for new features these
> response parameters can grow. Use a structure to pass these
> parameters
> rather than passing them as function arguments.
Applied, I added the new things to the documentation.
johannes
prev parent reply other threads:[~2017-03-31 6:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-30 21:22 [PATCH 1/2] cfg80211: Use a structure to pass connect response params Jouni Malinen
2017-03-30 21:22 ` [PATCH 2/2] cfg80211: Add support for FILS shared key authentication offload Jouni Malinen
2017-03-31 6:33 ` Johannes Berg
2017-03-31 6:32 ` 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=1490941921.24283.2.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=jouni@qca.qualcomm.com \
--cc=linux-wireless@vger.kernel.org \
--cc=vkanchan@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 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).