Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932750AbcKMEko (ORCPT ); Sat, 12 Nov 2016 23:40:44 -0500 Received: from shards.monkeyblade.net ([184.105.139.130]:59998 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932268AbcKMEkm (ORCPT ); Sat, 12 Nov 2016 23:40:42 -0500 Date: Sat, 12 Nov 2016 23:40:39 -0500 (EST) Message-Id: <20161112.234039.1001224346500132925.davem@davemloft.net> To: bhe@redhat.com Cc: netdev@vger.kernel.org, michael.chan@broadcom.com, linux-kernel@vger.kernel.org, Dept-GELinuxNICDev@cavium.com, rasesh.mody@cavium.com, harish.patil@cavium.com, frank@undermydesk.org, jsr@dex.edzone.net, pmenzel@molgen.mpg.de, jroedel@suse.de, dyoung@redhat.com Subject: Re: [PATCH v2 2/2] bnx2: Wait for in-flight DMA to complete at probe stage From: David Miller In-Reply-To: <20161113041524.GF15325@x1> References: <1478871995-29652-1-git-send-email-bhe@redhat.com> <1478871995-29652-3-git-send-email-bhe@redhat.com> <20161113041524.GF15325@x1> X-Mailer: Mew version 6.7 on Emacs 25.1 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Sat, 12 Nov 2016 19:41:12 -0800 (PST) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 803 Lines: 22 From: Baoquan He Date: Sun, 13 Nov 2016 12:15:24 +0800 > In-flight DMA from 1st kernel could continue going in kdump kernel. > New io-page table has been created before bnx2 does reset at open stage. > We have to wait for the in-flight DMA to complete to avoid it look up > into the newly created io-page table at probe stage. > > Suggested-by: Michael Chan > Signed-off-by: Baoquan He > --- > v1->v2: > Michael suggested to wait for the in-flight DMA to complete at probe > stage. So give up the old method of trying to reset chip at probe > stage, take the new way accordingly. Patch updates don't work this way. When you update a patch that is part of a patch series, you must resubmit the entire series anew. Thank you.