From: sashiko-bot@kernel.org
To: "Abhijit Gangurde" <abhijit.gangurde@amd.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [for-next v4 4/5] RDMA/ionic: add completion timestamp to CQE format
Date: Fri, 30 Oct 2026 04:54:27 +0000 [thread overview]
Message-ID: <sashiko-outbox-190466@kernel.org> (raw)
In-Reply-To: <20260610154216.712374-5-abhijit.gangurde@amd.com>
> Update the CQE structure to include hardware timestamp.
> When firmware supports RDMA completion timestamps,
> the hardware populates the timestamp field.
>
> Co-developed-by: Allen Hubbe <allen.hubbe@amd.com>
> Signed-off-by: Allen Hubbe <allen.hubbe@amd.com>
> Signed-off-by: Abhijit Gangurde <abhijit.gangurde@amd.com>
Sashiko has reviewed this patch and found no issues.
--
Sashiko AI review · https://sashiko.dev/#/patchset/20260610154216.712374-1-abhijit.gangurde@amd.com?part=4
next prev parent reply other threads:[~2026-10-30 4:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-10 15:42 [for-next v4 0/5] ionic: RDMA completion timestamping support Abhijit Gangurde
2026-06-10 15:42 ` [for-next v4 1/5] net: ionic: register PHC for rdma timestamping Abhijit Gangurde
2026-10-30 4:54 ` sashiko-bot
2026-06-10 15:42 ` [for-next v4 2/5] net: ionic: Add PHC state page for user space access Abhijit Gangurde
2026-10-30 4:54 ` sashiko-bot
2026-06-10 15:42 ` [for-next v4 3/5] RDMA/ionic: map PHC state into user space Abhijit Gangurde
2026-10-30 4:54 ` sashiko-bot
2026-06-10 15:42 ` [for-next v4 4/5] RDMA/ionic: add completion timestamp to CQE format Abhijit Gangurde
2026-10-30 4:54 ` sashiko-bot [this message]
2026-06-10 15:42 ` [for-next v4 5/5] RDMA/mlx5: move mlx5 clock info to common struct ib_uverbs_clock_info Abhijit Gangurde
2026-07-15 13:08 ` [for-next v4 0/5] ionic: RDMA completion timestamping support Abhijit Gangurde
2026-07-16 8:01 ` Leon Romanovsky
2026-07-16 8:56 ` Abhijit Gangurde
2026-07-16 9:19 ` Leon Romanovsky
2026-07-22 8:45 ` Abhijit Gangurde
2026-07-22 8:55 ` Leon Romanovsky
2026-07-22 8:56 ` Leon Romanovsky
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=sashiko-outbox-190466@kernel.org \
--to=sashiko-bot@kernel.org \
--cc=abhijit.gangurde@amd.com \
--cc=linux-rdma@vger.kernel.org \
--cc=sashiko-reviews@lists.linux.dev \
/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