From: Leon Romanovsky <leonro@mellanox.com>
To: Saeed Mahameed <saeedm@mellanox.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"linux-rdma@vger.kernel.org" <linux-rdma@vger.kernel.org>,
Jason Gunthorpe <jgg@mellanox.com>,
Tariq Toukan <tariqt@mellanox.com>
Subject: Re: [PATCH mlx5-next 3/4] IB/mlx5: Use helper to get CQE opcode
Date: Wed, 5 Dec 2018 08:09:20 +0000 [thread overview]
Message-ID: <20181205062304.GF15544@mtr-leonro.mtl.com> (raw)
In-Reply-To: <20181205020303.16318-4-saeedm@mellanox.com>
[-- Attachment #1: Type: text/plain, Size: 537 bytes --]
On Tue, Dec 04, 2018 at 06:03:02PM -0800, Saeed Mahameed wrote:
> From: Tariq Toukan <tariqt@mellanox.com>
>
> Use the new helper that extracts the opcode
> from a CQE (completion queue entry) structure.
>
> Signed-off-by: Tariq Toukan <tariqt@mellanox.com>
> Signed-off-by: Saeed Mahameed <saeedm@mellanox.com>
> ---
> drivers/infiniband/hw/mlx5/cq.c | 8 ++++----
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
I recommend you to squash this patch into the previous one.
Thanks,
Acked-by: Leon Romanovsky <leonro@mellanox.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 801 bytes --]
next prev parent reply other threads:[~2018-12-05 8:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-05 2:02 [PATCH mlx5-next 0/4] mlx5 core CQE API and misc updates Saeed Mahameed
2018-12-05 2:03 ` [PATCH mlx5-next 1/4] net/mlx5: When fetching CQEs return CQE instead of void pointer Saeed Mahameed
2018-12-05 2:03 ` [PATCH mlx5-next 2/4] net/mlx5: Use helper to get CQE opcode Saeed Mahameed
2018-12-05 4:55 ` Cong Wang
2018-12-05 22:37 ` Saeed Mahameed
2018-12-05 2:03 ` [PATCH mlx5-next 3/4] IB/mlx5: " Saeed Mahameed
2018-12-05 8:09 ` Leon Romanovsky [this message]
2018-12-05 22:27 ` Saeed Mahameed
2018-12-05 2:03 ` [PATCH mlx5-next 4/4] net/mlx5: Move flow counters data structures from flow steering header Saeed Mahameed
2018-12-05 5:04 ` Cong Wang
2018-12-05 22:26 ` Saeed Mahameed
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=20181205062304.GF15544@mtr-leonro.mtl.com \
--to=leonro@mellanox.com \
--cc=jgg@mellanox.com \
--cc=linux-rdma@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saeedm@mellanox.com \
--cc=tariqt@mellanox.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