From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 228372BC9 for ; Mon, 31 Jul 2017 19:53:16 +0200 (CEST) Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 31 Jul 2017 10:53:15 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.41,304,1498546800"; d="scan'208";a="113982470" Received: from fyigit-mobl1.ger.corp.intel.com (HELO [10.237.220.48]) ([10.237.220.48]) by orsmga004.jf.intel.com with ESMTP; 31 Jul 2017 10:53:14 -0700 To: Rasesh Mody , dev@dpdk.org Cc: Dept-EngDPDKDev@cavium.com, Thomas Monjalon References: <1500891548-21896-1-git-send-email-rasesh.mody@cavium.com> From: Ferruh Yigit Message-ID: Date: Mon, 31 Jul 2017 18:53:14 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <1500891548-21896-1-git-send-email-rasesh.mody@cavium.com> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-dev] [PATCH 1/7] net/qede/base: fix recovery from previous ungraceful exit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 31 Jul 2017 17:53:17 -0000 On 7/24/2017 11:19 AM, Rasesh Mody wrote: > This patch modifies the recovery flow to allow ongoing PCIe > transactions to be completed. To achieve this, the load sequence is > changed such that the "final_cleanup" notification is sent while the > FID_enable is cleared. > This change ensures that the chip cleanup actions takes place from > previous driver instance if needed. > > Fixes: ec94dbc57362 ("qede: add base driver") > > Signed-off-by: Rasesh Mody Series applied to dpdk-next-net/master, thanks. Except from patch 5/7, which Shahed Shaikh adds him as one of the driver maintainers. This is the first patch from "Shahed Shaikh", before getting this patch, I believe it is good to have explicit Acks from existing maintainers. And this is the process issue, not something that will effect the code, so it can be merged in next release or directly to main tree later by Thomas.