From: Thinh Tran <thinhtr@linux.vnet.ibm.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: aelior@marvell.com, davem@davemloft.net, edumazet@google.com,
manishc@marvell.com, netdev@vger.kernel.org, pabeni@redhat.com,
skalluru@marvell.com, VENKATA.SAI.DUGGI@ibm.com,
Abdul Haleem <abdhalee@in.ibm.com>,
David Christensen <drc@linux.vnet.ibm.com>,
Simon Horman <simon.horman@corigine.com>
Subject: Re: [Patch v6 0/4] bnx2x: Fix error recovering in switch configuration
Date: Wed, 17 Jan 2024 15:56:21 -0600 [thread overview]
Message-ID: <dd4d42ef-4c49-46fb-8e90-9b80c1315e92@linux.vnet.ibm.com> (raw)
In-Reply-To: <4bc40774-eae9-4134-be51-af23ad0b6f84@linux.vnet.ibm.com>
Hi all,
I hope this message finds you well. I'm reaching out to move forward
with these patches. If there are any remaining concerns or if
additional information is needed from my side, please let me know.
Your guidance on the next steps would be greatly appreciated.
Best regards,
Thinh Tran
On 11/16/2023 10:08 AM, 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.
>
> Thank you,
> Thinh Tran
next prev parent reply other threads:[~2024-01-17 21:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-16 16:08 [Patch v6 0/4] bnx2x: Fix error recovering in switch configuration Thinh Tran
2023-11-16 20:56 ` Simon Horman
2024-01-17 21:56 ` Thinh Tran [this message]
2024-01-17 23:55 ` Jakub Kicinski
2024-01-18 16:53 ` Thinh Tran
-- strict thread matches above, loose matches on Subject: below --
2023-07-28 21:11 [PATCH v4] " Thinh Tran
2023-08-18 16:14 ` [Patch v6 0/4] " Thinh Tran
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=dd4d42ef-4c49-46fb-8e90-9b80c1315e92@linux.vnet.ibm.com \
--to=thinhtr@linux.vnet.ibm.com \
--cc=VENKATA.SAI.DUGGI@ibm.com \
--cc=abdhalee@in.ibm.com \
--cc=aelior@marvell.com \
--cc=davem@davemloft.net \
--cc=drc@linux.vnet.ibm.com \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=manishc@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=simon.horman@corigine.com \
--cc=skalluru@marvell.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).