From: Jakub Kicinski <kuba@kernel.org>
To: Tariq Toukan <ttoukan.linux@gmail.com>
Cc: Tariq Toukan <tariqt@nvidia.com>,
"David S. Miller" <davem@davemloft.net>,
Paolo Abeni <pabeni@redhat.com>,
Eric Dumazet <edumazet@google.com>,
netdev@vger.kernel.org, Saeed Mahameed <saeedm@nvidia.com>,
Gal Pressman <gal@nvidia.com>,
Leon Romanovsky <leonro@nvidia.com>
Subject: Re: [PATCH net 6/7] net/mlx5e: Present succeeded IPsec SA bytes and packet
Date: Wed, 26 Jun 2024 06:45:08 -0700 [thread overview]
Message-ID: <20240626064508.06573a83@kernel.org> (raw)
In-Reply-To: <25bae4ee-f333-45ea-8c61-d9d520df08ae@gmail.com>
On Wed, 26 Jun 2024 15:54:32 +0300 Tariq Toukan wrote:
> > wrong commit ID, I think that it should be:
> >
> > Fixes: 6fb7f9408779 ("net/mlx5e: Connect mlx5 IPsec statistics with XFRM core")
>
> Right!
> Should I respin? Or can be fixed while being merged?
Please respin.
next prev parent reply other threads:[~2024-06-26 13:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-24 7:29 [PATCH net 0/7] mlx5 fixes 2024-06-24 Tariq Toukan
2024-06-24 7:29 ` [PATCH net 1/7] net/mlx5: IFC updates for changing max EQs Tariq Toukan
2024-06-24 7:29 ` [PATCH net 2/7] net/mlx5: Use max_num_eqs_24b capability if set Tariq Toukan
2024-06-24 7:29 ` [PATCH net 3/7] net/mlx5: Use max_num_eqs_24b when setting max_io_eqs Tariq Toukan
2024-06-24 7:29 ` [PATCH net 4/7] net/mlx5: E-switch, Create ingress ACL when needed Tariq Toukan
2024-06-24 7:29 ` [PATCH net 5/7] net/mlx5e: Add mqprio_rl cleanup and free in mlx5e_priv_cleanup() Tariq Toukan
2024-06-24 7:30 ` [PATCH net 6/7] net/mlx5e: Present succeeded IPsec SA bytes and packet Tariq Toukan
2024-06-26 0:21 ` Jakub Kicinski
2024-06-26 12:54 ` Tariq Toukan
2024-06-26 13:45 ` Jakub Kicinski [this message]
2024-06-24 7:30 ` [PATCH net 7/7] net/mlx5e: Approximate IPsec per-SA payload data bytes count Tariq Toukan
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=20240626064508.06573a83@kernel.org \
--to=kuba@kernel.org \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gal@nvidia.com \
--cc=leonro@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=ttoukan.linux@gmail.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).