From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E89EAC2BA1A for ; Fri, 24 Apr 2020 10:18:44 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id D00E720704 for ; Fri, 24 Apr 2020 10:18:44 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726614AbgDXKSl (ORCPT ); Fri, 24 Apr 2020 06:18:41 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59730 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-FAIL-OK-FAIL) by vger.kernel.org with ESMTP id S1726289AbgDXKSi (ORCPT ); Fri, 24 Apr 2020 06:18:38 -0400 Received: from sipsolutions.net (s3.sipsolutions.net [IPv6:2a01:4f8:191:4433::2]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 5BC73C09B045 for ; Fri, 24 Apr 2020 03:18:38 -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 1jRvPo-00FShF-B6; Fri, 24 Apr 2020 12:18:36 +0200 Message-ID: Subject: Re: [RFC PATCH 0/4] cfg80211: updates and fixes for TID specific configuration From: Johannes Berg To: Sergey Matyukevich , linux-wireless@vger.kernel.org Cc: Tamizh Chelvam Date: Fri, 24 Apr 2020 12:18:35 +0200 In-Reply-To: <20200420113437.16998-1-sergey.matyukevich.os@quantenna.com> References: <20200420113437.16998-1-sergey.matyukevich.os@quantenna.com> 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 Hi, > 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? johannes