Subject: Re: [PATCH 5/5] mac80211_hwsim: Ext Key ID support (NATIVE)
To:     Johannes Berg <johannes@sipsolutions.net>
Cc:     linux-wireless@vger.kernel.org
References: <20190316204208.16497-1-alexander@wetzel-home.de>
 <20190316204208.16497-6-alexander@wetzel-home.de>
 <d4db2ae373172afa8d2eb22e92a54a6f921784b7.camel@sipsolutions.net>
From:   Alexander Wetzel <alexander@wetzel-home.de>
Message-ID: <3ddf7283-7a35-cb0e-a7a1-d682f6bf9582@wetzel-home.de>
Date:   Tue, 19 Mar 2019 21:44:07 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101
 Thunderbird/60.5.3
MIME-Version: 1.0
In-Reply-To: <d4db2ae373172afa8d2eb22e92a54a6f921784b7.camel@sipsolutions.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Sender: linux-wireless-owner@vger.kernel.org
Precedence: bulk

>> Driver is not supporting hardware encryption and therefore fully
>> compatible with Extended Key ID.
> 
> On this particular patch now reading this I'm wondering if we shouldn't
> just do that in mac80211 if there's no set_key callback? I suspect
> that'd affect a few drivers that are otherwise more or less orphaned.

Good idea.
It's costing next to nothing to enable it for for drivers without a 
set_key() callback, so I've just released v2 of the patch doing exactly 
that. I kept all the information what has changed since the last RFC 
series in the cover letter and the patches, so you can just ignore v1 of 
the patch and directly move to v2.

Alexander