Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932705AbcKMEyf (ORCPT ); Sat, 12 Nov 2016 23:54:35 -0500 Received: from mx1.redhat.com ([209.132.183.28]:49506 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753676AbcKMEye (ORCPT ); Sat, 12 Nov 2016 23:54:34 -0500 Date: Sun, 13 Nov 2016 12:54:29 +0800 From: Baoquan He To: David Miller 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 Message-ID: <20161113045429.GG15325@x1> References: <1478871995-29652-1-git-send-email-bhe@redhat.com> <1478871995-29652-3-git-send-email-bhe@redhat.com> <20161113041524.GF15325@x1> <20161112.234039.1001224346500132925.davem@davemloft.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161112.234039.1001224346500132925.davem@davemloft.net> User-Agent: Mutt/1.7.0 (2016-08-17) X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.28]); Sun, 13 Nov 2016 04:54:33 +0000 (UTC) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1029 Lines: 29 On 11/12/16 at 11:40pm, David Miller wrote: > 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. Thanks for telling, David! Learned it. I am not very sure if this is what Michael is suggesting. Will resubmit the entire patch series. Thanks Baoquan