From: Jakub Kicinski <kuba@kernel.org>
To: Thinh Tran <thinhtr@linux.vnet.ibm.com>
Cc: netdev@vger.kernel.org, aelior@marvell.com, davem@davemloft.net,
manishc@marvell.com, pabeni@redhat.com, skalluru@marvell.com,
simon.horman@corigine.com, edumazet@google.com,
VENKATA.SAI.DUGGI@ibm.com, drc@linux.vnet.ibm.com,
abdhalee@in.ibm.com
Subject: Re: [PATCH v8 1/2] net/bnx2x: Prevent access to a freed page in page_pool
Date: Thu, 8 Feb 2024 17:29:36 -0800 [thread overview]
Message-ID: <20240208172936.7a8b7fb8@kernel.org> (raw)
In-Reply-To: <056b4e86-a894-4a4b-a8dd-81f440118106@linux.vnet.ibm.com>
On Thu, 8 Feb 2024 13:18:14 -0600 Thinh Tran wrote:
> Fixes: 4cace675d687 ("bnx2x: Alloc 4k fragment for each rx ring buffer
> element")
The Fixes tag should be on one line, without wrapping.
Please post a v9 with the tag included, as a new thread.
Don't use --in-reply-to on netdev (sorry for so many rules..)
next prev parent reply other threads:[~2024-02-09 1:29 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 17:48 [PATCH v7 0/2] bnx2x: Fix error recovering in switch configuration Thinh Tran
2024-02-01 17:48 ` [PATCH v7 1/2] net/bnx2x: Prevent access to a freed page in page_pool Thinh Tran
2024-02-08 2:37 ` Jakub Kicinski
2024-02-01 17:48 ` [PATCH v7 2/2] net/bnx2x: refactor common code to bnx2x_stop_nic() Thinh Tran
2024-02-08 18:55 ` [PATCH v8 0/2] bnx2x: Fix error recovering in switch configuration Thinh Tran
2024-02-12 20:47 ` [PATCH v9 " Thinh Tran
2024-02-08 18:55 ` [PATCH v8 1/2] net/bnx2x: Prevent access to a freed page in page_pool Thinh Tran
2024-02-12 20:47 ` [PATCH v9 " Thinh Tran
2024-02-08 19:14 ` [PATCH v8 " Thinh Tran
2024-02-08 19:18 ` Thinh Tran
2024-02-09 1:29 ` Jakub Kicinski [this message]
2024-02-12 20:47 ` Thinh Tran
2024-02-08 18:55 ` [PATCH v8 2/2] net/bnx2x: refactor common code to bnx2x_stop_nic() Thinh Tran
2024-02-12 20:47 ` [PATCH v9 " 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=20240208172936.7a8b7fb8@kernel.org \
--to=kuba@kernel.org \
--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=manishc@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=simon.horman@corigine.com \
--cc=skalluru@marvell.com \
--cc=thinhtr@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.