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 969A5A052A; Tue, 2 Feb 2021 06:46:59 +0100 (CET) Received: from [217.70.189.124] (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 5F320240240; Tue, 2 Feb 2021 06:46:59 +0100 (CET) Received: from mga12.intel.com (mga12.intel.com [192.55.52.136]) by mails.dpdk.org (Postfix) with ESMTP id 26A4924023F for ; Tue, 2 Feb 2021 06:46:57 +0100 (CET) IronPort-SDR: LFcacj8yzWhyMTncqrDx0gT9yOq8ccC1+pvBdf9oppsg3MrihvWOWKzjWX7JVBi0TNk+3LtN1k Xo8T6itlkFYg== X-IronPort-AV: E=McAfee;i="6000,8403,9882"; a="159968509" X-IronPort-AV: E=Sophos;i="5.79,394,1602572400"; d="scan'208";a="159968509" Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga106.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 01 Feb 2021 21:46:56 -0800 IronPort-SDR: f6ibtkMqfl+0ufdLoXkRnjESMFd5BpIC4ET90bOCxbGnDawEW9Kb42NDPSkLYhe3Ip7pXzGMQw wcWeSYyvBNoA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.79,394,1602572400"; d="scan'208";a="412922095" Received: from fmsmsx606.amr.corp.intel.com ([10.18.126.86]) by fmsmga002.fm.intel.com with ESMTP; 01 Feb 2021 21:46:56 -0800 Received: from shsmsx604.ccr.corp.intel.com (10.109.6.214) by fmsmsx606.amr.corp.intel.com (10.18.126.86) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2106.2; Mon, 1 Feb 2021 21:46:56 -0800 Received: from shsmsx601.ccr.corp.intel.com (10.109.6.141) by SHSMSX604.ccr.corp.intel.com (10.109.6.214) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1713.5; Tue, 2 Feb 2021 13:46:54 +0800 Received: from shsmsx601.ccr.corp.intel.com ([10.109.6.141]) by SHSMSX601.ccr.corp.intel.com ([10.109.6.141]) with mapi id 15.01.1713.004; Tue, 2 Feb 2021 13:46:54 +0800 From: "Tu, Lijuan" To: "Fu, Qi" , "dts@dpdk.org" CC: "Fu, Qi" Thread-Topic: [dts] [PATCH V1]test_plans/cvl_advanced_iavf_rss_gtpu_test_plan:remove steps of destroy rss rules for gtpu cases Thread-Index: AQHW9US2FrqspcHkiUSMipR9q45BvqpEYwCQ Date: Tue, 2 Feb 2021 05:46:54 +0000 Message-ID: <2a003e28aedc4344942cc6c93371ce7b@intel.com> References: <20210128155539.27471-1-qi.fu@intel.com> In-Reply-To: <20210128155539.27471-1-qi.fu@intel.com> Accept-Language: zh-CN, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: dlp-reaction: no-action dlp-version: 11.5.1.3 dlp-product: dlpe-windows x-originating-ip: [10.239.127.36] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dts] [PATCH V1]test_plans/cvl_advanced_iavf_rss_gtpu_test_plan:remove steps of destroy rss rules for gtpu cases X-BeenThere: dts@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: test suite reviews and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dts-bounces@dpdk.org Sender: "dts" > synced with developer, the behavior after destroy rss rules are not unifi= ed. > so delete the steps after destroying rss rules. >=20 > Signed-off-by: qifu Applied, thanks