From: Ariel D'Alessandro <ariel.dalessandro@collabora.com>
To: Daniel Wagner <wagi@monom.org>
Cc: connman@lists.linux.dev, iwd@lists.01.org,
Sven.Dembianny@bshg.com, andrew.shadura@collabora.co.uk,
niraj.g@samsung.com, n.chaprana@samsung.com, marcel@holtmann.org
Subject: Re: [RFC connman v2 1/1] WIP: Add wpa_supplicant WPA3-SAE support
Date: Mon, 14 Jun 2021 08:50:10 -0300 [thread overview]
Message-ID: <d7977fbd-3d03-e9d9-8a5e-1222707eb285@collabora.com> (raw)
In-Reply-To: <20210614070042.mtst3o4utquyzfkq@beryllium.lan>
Hi Daniel,
On 6/14/21 4:00 AM, Daniel Wagner wrote:
> Hi Ariel,
>
> On Thu, May 27, 2021 at 06:41:34PM -0300, Ariel D'Alessandro wrote:
>> Implement WPA3-SAE authentication on connman side using wpa_supplicant
>> backend.
>>
>> Initially based on Tizen project:
>>
>> https://review.tizen.org/git/?p=platform/upstream/connman.git
>>
>> Signed-off-by: Ariel D'Alessandro <ariel.dalessandro@collabora.com>
>
> We don't do the SOB, so I just dropped.
Ok.
>
> I applied the patch, there were small style issues which I fixed it
> directly.
Great! Thanks a lot for your help.
>
> Probably we should update the documentation which wpa_supplicant version
> is needed to support WPA3.
Which doc files should be updated? I can take a look at that and put
some notes together.
Regards,
Ariel
next prev parent reply other threads:[~2021-06-14 11:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210527214134.33792-1-ariel.dalessandro@collabora.com>
[not found] ` <20210527214134.33792-2-ariel.dalessandro@collabora.com>
2021-06-14 7:00 ` [RFC connman v2 1/1] WIP: Add wpa_supplicant WPA3-SAE support Daniel Wagner
2021-06-14 11:50 ` Ariel D'Alessandro [this message]
2021-06-14 11:57 ` Daniel Wagner
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=d7977fbd-3d03-e9d9-8a5e-1222707eb285@collabora.com \
--to=ariel.dalessandro@collabora.com \
--cc=Sven.Dembianny@bshg.com \
--cc=andrew.shadura@collabora.co.uk \
--cc=connman@lists.linux.dev \
--cc=iwd@lists.01.org \
--cc=marcel@holtmann.org \
--cc=n.chaprana@samsung.com \
--cc=niraj.g@samsung.com \
--cc=wagi@monom.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;
as well as URLs for NNTP newsgroup(s).