Received: by 2002:a25:1985:0:0:0:0:0 with SMTP id 127csp459050ybz; Fri, 24 Apr 2020 03:30:36 -0700 (PDT) X-Google-Smtp-Source: APiQypJE+/YQLA2oSmqCjxicNdb5IdD2XSmWIXLaa2d7xA60PeeqYWRCYcAHcfWglqTITcv1ERgl X-Received: by 2002:aa7:d514:: with SMTP id y20mr6642632edq.28.1587724236053; Fri, 24 Apr 2020 03:30:36 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1587724236; cv=none; d=google.com; s=arc-20160816; b=Lj1++bAnYm1VEGMKd3oA7fB0SOM27w9A9kK4kOZP9x/5ZXuJbl0UKx8/OzaLPaJmD9 DICSbcyMLH5YQTR/irFQvRAiClDGK12ZA1kQUcS1SE8FtbKzxEIoSQS02sZol55vAWDY cTwznZCsiqg6hW5m7SoHvILx1/gefICyPGZQJ8qmG4OtI7h67yExz+iZENHlOMTrRNh5 KSYutFYlzdTZjnFLBSbDiQVLgGV96XeECNOUHGRnITMMaYeAhdGeeJt+ogjpbIm1XLFV vznX8mVE1mlKN22ZS+evDNI7IuuQLtD489BzoaNpmjSk3wix1o/A4YQ+XG4Oy1e2xCp4 Il/w== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :user-agent:references:in-reply-to:date:cc:to:from:subject :message-id; bh=clZEpfFM6GNuAAtqpvz1hyqW/lsIXp+8JgM28T1alpk=; b=seOut4Wzwiy2PMHSiQ5fWZfq2IbCMRHZJuWX0ihQjxTMifr6+cdv59uONR2Ro+6b0+ VVsBY0/sJC8EeUHouQzi903e0CI3WJsZjRjr329OwF0NLX1SbuNC6W6SsrG/IHZCT8hX eFclheMDoj36J49QTxw6ROP3Z7Z7Kx9mbcd4j++aPmMnRb2uwUSzw7qwHfDvzYEk2vxR /CVdQ4YF+HA/IDdFalWya3UiUvub7TNIHTJTSPsBaRmq5+boBt6irxLn2kqqgeP8/Ln/ W0XtzSIFFfsZ/QJp6klciAVl0ivXtCvQFhX77TiJ+UU+yme2xu2OWrGJIbZI+Wuma9cA Ob5g== ARC-Authentication-Results: i=1; mx.google.com; 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 Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id s20si2613837edr.444.2020.04.24.03.30.11; Fri, 24 Apr 2020 03:30:36 -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; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726614AbgDXKaD (ORCPT + 99 others); Fri, 24 Apr 2020 06:30:03 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:33244 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726193AbgDXKaC (ORCPT ); Fri, 24 Apr 2020 06:30:02 -0400 Received: from sipsolutions.net (s3.sipsolutions.net [IPv6:2a01:4f8:191:4433::2]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id C2A9DC09B045 for ; Fri, 24 Apr 2020 03:30:02 -0700 (PDT) Received: by sipsolutions.net with esmtpsa (TLS1.3:ECDHE_SECP256R1__RSA_PSS_RSAE_SHA256__AES_256_GCM:256) (Exim 4.93) (envelope-from ) id 1jRvap-00FSyW-6U; Fri, 24 Apr 2020 12:30:00 +0200 Message-ID: <0ae5ad298361f94c58d21233a4aea6f5a18e9522.camel@sipsolutions.net> Subject: Re: [RFC PATCH 0/4] cfg80211: updates and fixes for TID specific configuration From: Johannes Berg To: Sergey Matyukevich Cc: linux-wireless@vger.kernel.org, Tamizh Chelvam Date: Fri, 24 Apr 2020 12:29:57 +0200 In-Reply-To: <20200424102636.lua5qdeaw2fkl7kn@bars> References: <20200420113437.16998-1-sergey.matyukevich.os@quantenna.com> <20200424102636.lua5qdeaw2fkl7kn@bars> Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.34.4 (3.34.4-1.fc31) MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Sender: linux-wireless-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-wireless@vger.kernel.org On Fri, 2020-04-24 at 13:26 +0300, Sergey Matyukevich wrote: > > > This patch series contains several minor fixes and enhancements for TID > > > specific configuration functionality. The first three patches include > > > minor fixes and TID specific AMSDU configuration. > > > > Looks good, though I just saw you noticed a small bug :) > > > > > The last patch is somewhat controversial, so the series is marked as RFC. > > > The last patch simplifies current override logic. It suggests to make no > > > difference between 'specific peer' and 'all peers' cases and to apply > > > new TID configuration immediately after resetting the previous one. > > > > Yeah, I tend to agree. > > > > Can you resend with the small fix? > > Sure, will do. Is it ok if I add a patch supporting this feature in iw tool ? > Or you would prefer to review it separately after this series lands in > mac80211-next ? That's fine. Not sure how you could possibly send them in the same series with git, but go ahead :) FWIW, I will always ignore nl80211.h update patches, I do those myself, so no need to send that. johannes