Received: by 2002:a05:6a10:5bc5:0:0:0:0 with SMTP id os5csp1723530pxb; Fri, 22 Oct 2021 06:31:04 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzTz/dkx2bsIsqhSzQqiWtlDk3eOPwcfB+5pNwmHNsDwP26Dry3yy49xbQXobG9No/GA0nO X-Received: by 2002:a17:907:1b16:: with SMTP id mp22mr15554777ejc.487.1634909464748; Fri, 22 Oct 2021 06:31:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1634909464; cv=none; d=google.com; s=arc-20160816; b=HD4l1WoXD92sefrIhqYFxrS3iuV5HNmpm5vCtbhmunJyr3GQzu9u6osOSBpuTbpCbT i7x26zcrkODHsZJbNWrxVXRpXzhWyaMoENXn/JjuKfimz02kEDr5GRQ4KJAczUIld7SZ x2xKSxy5THVcEQryN3IFX9/dly/6xL4EfBsWHzoiA6p/xbyeqv5AlK0/QtkXY+ycx02J 5Gk8ymQN3lup0jVByIONuq4AkWmioNNG4/r1kPGytYTHX0kTNv55bt7jn4fw4jgcs6xn u1++p64if4aaTcJ9sZ/m/sxMsaLRh7U72A5RXOoIgJQFKEzatY8KCRObV4TGKzs9l5eM FrYg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id:dkim-signature; bh=z30IKZGWWfA5CPoRtU28VazMVrjKYnEr/SB3kukIQig=; b=nBbc+fYV0zlgoHNnpM1D02sO7yi8D9QvHaG+mTnRsjDBXuOpYNjz5G72YUOE6iDcmF CMqVCu5BKMk+p5kPWdlZlWjF2JHQ3a1EWjrncp9/HbR4/NQhDZuXmrh18itUnkShV+yl z28HLQJMPz5nHgP32xmM0V/zKvbBzGidx92Q/6pkQ5WNfHieWKwbkHrIhvfsE4jy8aoT Qe4Bv6FcMMKlUuVfKtX3tims7lOnX/0XVIkHYTSFFEjQ2PngyiVsFg3qBOtcQqVSlGJ0 0p8iE+Tr54OJrQSlA5mXJgGtIdSr+eG4LqdOX5jATrdJLkN4NBqMkPXRTyisIoYb3jfz H+6A== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@sipsolutions.net header.s=mail header.b=XJVt5rlU; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=REJECT dis=NONE) header.from=sipsolutions.net Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id z23si12438599edm.184.2021.10.22.06.30.49; Fri, 22 Oct 2021 06:31:04 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@sipsolutions.net header.s=mail header.b=XJVt5rlU; spf=pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-wireless-owner@vger.kernel.org; dmarc=pass (p=NONE sp=REJECT dis=NONE) header.from=sipsolutions.net Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S232123AbhJVNcV (ORCPT + 64 others); Fri, 22 Oct 2021 09:32:21 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:40826 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230264AbhJVNcU (ORCPT ); Fri, 22 Oct 2021 09:32:20 -0400 Received: from sipsolutions.net (s3.sipsolutions.net [IPv6:2a01:4f8:191:4433::2]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 10C3FC061764 for ; Fri, 22 Oct 2021 06:30:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=sipsolutions.net; s=mail; h=Content-Transfer-Encoding:MIME-Version: Content-Type:References:In-Reply-To:Date:Cc:To:From:Subject:Message-ID:Sender :Reply-To:Content-ID:Content-Description:Resent-Date:Resent-From:Resent-To: Resent-Cc:Resent-Message-ID; bh=z30IKZGWWfA5CPoRtU28VazMVrjKYnEr/SB3kukIQig=; t=1634909403; x=1636119003; b=XJVt5rlUGR3XE0W7cBvdFq9NyGuzJUaJmXjRQRhWN43FJeq e2kbUEXv1lM3tXvy+0EsYTwy7h5oL/yMWZVfqvVsq+R+lY5+CiRAdW6F8Q8Sg6r3bcW6XcoW40bGP RHyERHYr1vZaVNTW6sNizCCQsB1UlyNsfhKHuyOdcHyxMiSWFKKh8TcHc1KmyKDcJRt3nTxUajbmR i0CDHMFor5JJf4GAQOy1PJ2nng3wR8hitkvC6FTvl3Dw7Ku6mNTv83357eZCs8i2r0calEmjFSVr7 8/nhoW9rHp1E57xuVxN0abktGeEEhnlLxuzhxWt3PXKZ82UU7byH2GWFtk7Zq4Cw==; Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.95) (envelope-from ) id 1mducS-005ftE-Ow; Fri, 22 Oct 2021 15:30:00 +0200 Message-ID: <69995d6c767edcea15ef7645fabc0e39c0dc7960.camel@sipsolutions.net> Subject: Re: [PATCH] nl80211: Indicate SA Query procedures offload for AP SME device From: Johannes Berg To: vjakkam@codeaurora.org Cc: linux-wireless@vger.kernel.org Date: Fri, 22 Oct 2021 15:29:59 +0200 In-Reply-To: <5a1f654e3406e99c816afbc762519fea@codeaurora.org> References: <1634210331-9001-1-git-send-email-vjakkam@codeaurora.org> <612e80125878bae6fccbb72701381832a8a6029c.camel@sipsolutions.net> <5a1f654e3406e99c816afbc762519fea@codeaurora.org> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.38.4 (3.38.4-1.fc33) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-malware-bazaar: not-scanned Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Fri, 2021-10-22 at 18:56 +0530, vjakkam@codeaurora.org wrote: > > > > So how's that going to work with older hostapd? It'll be offloaded, and > > then hostapd doesn't know, so it's still going to disconnect them? > > > > So should be that hostapd also opts in to this driver behaviour? > > yes, we have to update hostapd also with new implementation based on the > feature flag. That wasn't my question. My question was what happens if you have a hostapd that's *not* updated?> johannes