From: Subbaraya Sundeep <sbhatta@marvell.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: <davem@davemloft.net>, <netdev@vger.kernel.org>,
<edumazet@google.com>, <pabeni@redhat.com>,
<andrew+netdev@lunn.ch>, <horms@kernel.org>, <shayagr@amazon.com>,
<akiyano@amazon.com>, <darinzon@amazon.com>,
<skalluru@marvell.com>, <manishc@marvell.com>,
<michael.chan@broadcom.com>, <pavan.chebbi@broadcom.com>,
<sgoutham@marvell.com>, <gakula@marvell.com>,
<hkelam@marvell.com>, <bbhushan2@marvell.com>
Subject: Re: [PATCH net-next 1/5] eth: bnx2x: migrate to new RXFH callbacks
Date: Wed, 18 Jun 2025 10:03:38 +0000 [thread overview]
Message-ID: <aFKO-lWjm4aYXHZj@de6bfc3b068f> (raw)
In-Reply-To: <20250617151428.499f80c2@kernel.org>
On 2025-06-17 at 22:14:28, Jakub Kicinski (kuba@kernel.org) wrote:
> On Tue, 17 Jun 2025 06:40:03 +0000 Subbaraya Sundeep wrote:
> > > The driver as no other RXNFC functionality so the SET callback can
> > typo as -> has
>
> I'll fix when applying, thanks
Since there wont be v2, for patchset
Reviewed-by: Subbaraya Sundeep <sbhatta@marvell.com>
Thanks,
Sundeep
next prev parent reply other threads:[~2025-06-18 10:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 1:45 [PATCH net-next 0/5] eth: migrate some drivers to new RXFH callbacks Jakub Kicinski
2025-06-17 1:45 ` [PATCH net-next 1/5] eth: bnx2x: migrate " Jakub Kicinski
2025-06-17 6:40 ` Subbaraya Sundeep
2025-06-17 22:14 ` Jakub Kicinski
2025-06-18 10:03 ` Subbaraya Sundeep [this message]
2025-06-17 1:45 ` [PATCH net-next 2/5] eth: bnxt: " Jakub Kicinski
2025-06-17 21:39 ` Michael Chan
2025-06-17 1:45 ` [PATCH net-next 3/5] eth: ena: " Jakub Kicinski
2025-06-17 6:50 ` Subbaraya Sundeep
2025-06-17 7:35 ` Arinzon, David
2025-06-17 1:45 ` [PATCH net-next 4/5] eth: thunder: " Jakub Kicinski
2025-06-17 6:43 ` Subbaraya Sundeep
2025-06-17 1:45 ` [PATCH net-next 5/5] eth: otx2: " Jakub Kicinski
2025-06-18 20:30 ` [PATCH net-next 0/5] eth: migrate some drivers " patchwork-bot+netdevbpf
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=aFKO-lWjm4aYXHZj@de6bfc3b068f \
--to=sbhatta@marvell.com \
--cc=akiyano@amazon.com \
--cc=andrew+netdev@lunn.ch \
--cc=bbhushan2@marvell.com \
--cc=darinzon@amazon.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=horms@kernel.org \
--cc=kuba@kernel.org \
--cc=manishc@marvell.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=sgoutham@marvell.com \
--cc=shayagr@amazon.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