From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 646C6A0567 for ; Wed, 10 Mar 2021 10:34:58 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 51DEF40687; Wed, 10 Mar 2021 10:34:58 +0100 (CET) Received: from youngberry.canonical.com (youngberry.canonical.com [91.189.89.112]) by mails.dpdk.org (Postfix) with ESMTP id A083440687 for ; Wed, 10 Mar 2021 10:34:57 +0100 (CET) Received: from mail-qv1-f71.google.com ([209.85.219.71]) by youngberry.canonical.com with esmtps (TLS1.2:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.86_2) (envelope-from ) id 1lJvF3-00082Q-7C for stable@dpdk.org; Wed, 10 Mar 2021 09:34:57 +0000 Received: by mail-qv1-f71.google.com with SMTP id i1so12276782qvu.12 for ; Wed, 10 Mar 2021 01:34:57 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=62l/PseMtsDdbKl3BoMo/uEVUsnpWArrMrnJn0HYm9E=; b=HuvE+pA+7XyQTeUx5s1s/QOUGycEtJU7Fk2iHJdEI074+QMycolTF0dMklZ/sIGbG3 8La5avBFt78cuTYkmZO6/qjYmTeXpBJBb6EVyngwTQPBZn/Bm4lpKKyivn7oldCiXBqR zBIHoZXzZhCi2edAzB23Jc1xyqV8mlpECA3QHdqCbazz7PjPvT/Aj0/MRHDbWWHh+ikr vbU7Ra9rtZUib7wff6mZPmK6ffBo/4EojdQgmi7qru0vhDeBUTneZpeIaq4c1YzC+tyt uNkjcHEYg77xUzcsqU3h2OYswR9SXi1+oTPsHKjVlyJp0sArYMdaQYLoapl6vfzSFmx8 0Edg== X-Gm-Message-State: AOAM5336lnMJ0jBmVtB2hkUT1ghZsEDJq18LFm8s+zSdi9fRHTG2/uWn Akg6VLHB7g70i7H4EjLJL4vkr7jKIqxL8GzX52AzTnuTPMFlTK8LkU+wj44h5EsioRIdD4Llwuw YbXqzfHOVQTYsU+R4f9Gt/w5nyKNA7IpIzv1EhBh4 X-Received: by 2002:a05:620a:16dc:: with SMTP id a28mr1719207qkn.442.1615368896387; Wed, 10 Mar 2021 01:34:56 -0800 (PST) X-Google-Smtp-Source: ABdhPJx0xaZ01NTAPN99t5AUaL+LE4KEqqxb3FIxEqlbLShRTqiYIgDGQARvd8CBw8qu5Z5qeGrjUxWsOWWOJnaxOUM= X-Received: by 2002:a05:620a:16dc:: with SMTP id a28mr1719187qkn.442.1615368896154; Wed, 10 Mar 2021 01:34:56 -0800 (PST) MIME-Version: 1.0 References: <20210204112954.2488123-1-christian.ehrhardt@canonical.com> <20210204112954.2488123-125-christian.ehrhardt@canonical.com> In-Reply-To: From: Christian Ehrhardt Date: Wed, 10 Mar 2021 10:34:30 +0100 Message-ID: To: Ali Alnubani Cc: Ori Kam , Ajit Khaparde , dpdk stable , Asaf Penso , Gregory Etelson Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-stable] patch 'app/testpmd: release flows left before port stop' has been queued to stable release 19.11.7 X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: stable-bounces@dpdk.org Sender: "stable" On Tue, Mar 9, 2021 at 9:33 AM Ali Alnubani wrote: > > > -----Original Message----- > > From: stable On Behalf Of Christian Ehrhardt > > Sent: Thursday, February 4, 2021 1:30 PM > > To: Gregory Etelson > > Cc: Ori Kam ; Ajit Khaparde > > ; dpdk stable > > Subject: [dpdk-stable] patch 'app/testpmd: release flows left before port > > stop' has been queued to stable release 19.11.7 > > > > Hi, > > > > FYI, your patch has been queued to stable release 19.11.7 > > > > Note it hasn't been pushed to http://dpdk.org/browse/dpdk-stable yet. > > It will be pushed if I get no objections before 02/06/21. So please > > shout if anyone has objections. > > > > Also note that after the patch there's a diff of the upstream commit vs the > > patch applied to the branch. This will indicate if there was any rebasing > > needed to apply to the stable branch. If there were code changes for > > rebasing > > (ie: not only metadata diffs), please double check that the rebase was > > correctly done. > > > > Queued patches are on a temporary branch at: > > https://github.com/cpaelzer/dpdk-stable-queue > > > > This queued commit can be viewed at: > > https://github.com/cpaelzer/dpdk-stable- > > queue/commit/ba53d40b4eb900d12beeb707c3cb163e421e6e85 > > > > Thanks. > > > > Christian Ehrhardt > > > > --- > > Hi Christian, > > We would like to drop this patch from 19.11 since it's a new feature. Would that be possible? Should we send a patch that reverts it? Hi, you don't need to send a revert, I can do that. Thanks for the IRC discussion btw! The one thing that might be worth is that you've said it is a new feature that should not be added, but just reading the patch description it sounds like just a fix. If you would not mind for some kind of trail (if we ever wonder) replying here with a bit more extended reasoning would be helpful. > Sorry we didn't respond ahead of time. > > Thanks, > Ali -- Christian Ehrhardt Staff Engineer, Ubuntu Server Canonical Ltd