[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20231116205608.GJ109951@vergenet.net>
Date: Thu, 16 Nov 2023 20:56:08 +0000
From: Simon Horman <horms@...nel.org>
To: Thinh Tran <thinhtr@...ux.vnet.ibm.com>
Cc: Jakub Kicinski <kuba@...nel.org>, aelior@...vell.com,
davem@...emloft.net, edumazet@...gle.com, manishc@...vell.com,
netdev@...r.kernel.org, pabeni@...hat.com, skalluru@...vell.com,
VENKATA.SAI.DUGGI@....com, Abdul Haleem <abdhalee@...ibm.com>,
David Christensen <drc@...ux.vnet.ibm.com>
Subject: Re: [Patch v6 0/4] bnx2x: Fix error recovering in switch
configuration
On Thu, Nov 16, 2023 at 10:08:34AM -0600, Thinh Tran wrote:
> Hi,
>
> Could we proceed with advancing these patches? They've been in the
> "Awaiting Upstream" state for a while now. Notably, one of them has
> successfully made it to the mainline kernel:
> [v6,1/4] bnx2x: new flag for tracking HW resource
>
> https://github.com/torvalds/linux/commit/bf23ffc8a9a777dfdeb04232e0946b803adbb6a9
>
> As testing the latest kernel, we are still encountering crashes due to
> the absence of one of the patches:
> [v6,3/4] bnx2x: Prevent access to a freed page in page_pool.
>
> Is there anything specific I need to do to help moving these patches
> forward?
> We would greatly appreciate if they could be incorporated into the
> mainline kernel.
Hi Thinh Tran,
I'd suggest that the best way to move this forwards would
be to rebase the remaining patches on net-next and posting them as a v7.
It would be useful to include the information above in the cover letter.
And to annotate that they are targeting net-next in the subject of
each patch and the cover letter.
Subject: [PATCH net-next v8 x/3] ...
Powered by blists - more mailing lists