[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20161112.234039.1001224346500132925.davem@davemloft.net>
Date: Sat, 12 Nov 2016 23:40:39 -0500 (EST)
From: David Miller <davem@...emloft.net>
To: bhe@...hat.com
Cc: netdev@...r.kernel.org, michael.chan@...adcom.com,
linux-kernel@...r.kernel.org, Dept-GELinuxNICDev@...ium.com,
rasesh.mody@...ium.com, harish.patil@...ium.com,
frank@...ermydesk.org, jsr@....edzone.net, pmenzel@...gen.mpg.de,
jroedel@...e.de, dyoung@...hat.com
Subject: Re: [PATCH v2 2/2] bnx2: Wait for in-flight DMA to complete at
probe stage
From: Baoquan He <bhe@...hat.com>
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 <michael.chan@...adcom.com>
> Signed-off-by: Baoquan He <bhe@...hat.com>
> ---
> 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.
Powered by blists - more mailing lists