From: Jason Gunthorpe <jgg@nvidia.com>
To: Leon Romanovsky <leon@kernel.org>
Cc: Doug Ledford <dledford@redhat.com>,
Leon Romanovsky <leonro@nvidia.com>,
Aharon Landau <aharonl@nvidia.com>, <linux-rdma@vger.kernel.org>,
"Maor Gottlieb" <maorg@nvidia.com>, <netdev@vger.kernel.org>,
Saeed Mahameed <saeedm@nvidia.com>
Subject: Re: [PATCH rdma-next 0/2] Real time/free running timestamp support
Date: Fri, 12 Feb 2021 14:10:56 -0400 [thread overview]
Message-ID: <20210212181056.GB1737478@nvidia.com> (raw)
In-Reply-To: <20210209131107.698833-1-leon@kernel.org>
On Tue, Feb 09, 2021 at 03:11:05PM +0200, Leon Romanovsky wrote:
> From: Leon Romanovsky <leonro@nvidia.com>
>
> Add an extra timestamp format for mlx5_ib device.
>
> Thanks
>
> Aharon Landau (2):
> net/mlx5: Add new timestamp mode bits
> RDMA/mlx5: Fail QP creation if the device can not support the CQE TS
>
> drivers/infiniband/hw/mlx5/qp.c | 104 +++++++++++++++++++++++++++++---
> include/linux/mlx5/mlx5_ifc.h | 54 +++++++++++++++--
> 2 files changed, 145 insertions(+), 13 deletions(-)
Since this is a rdma series, and we are at the end of the cycle, I
took the IFC file directly to the rdma tree instead of through the
shared branch.
Applied to for-next, thanks
Jason
next prev parent reply other threads:[~2021-02-12 18:12 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-09 13:11 [PATCH rdma-next 0/2] Real time/free running timestamp support Leon Romanovsky
2021-02-09 13:11 ` [PATCH mlx5-next 1/2] net/mlx5: Add new timestamp mode bits Leon Romanovsky
2021-02-09 18:28 ` Jakub Kicinski
2021-02-09 19:14 ` Leon Romanovsky
2021-02-09 19:52 ` Jakub Kicinski
2021-02-10 8:01 ` Leon Romanovsky
2021-02-09 13:11 ` [PATCH rdma-next 2/2] RDMA/mlx5: Fail QP creation if the device can not support the CQE TS Leon Romanovsky
2021-02-12 18:10 ` Jason Gunthorpe [this message]
2021-02-12 21:09 ` [PATCH rdma-next 0/2] Real time/free running timestamp support Saeed Mahameed
2021-02-12 21:14 ` Jason Gunthorpe
2021-02-12 21:19 ` Saeed Mahameed
2021-02-12 21:21 ` Jason Gunthorpe
2021-02-14 6:41 ` Leon Romanovsky
2021-02-16 14:12 ` 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=20210212181056.GB1737478@nvidia.com \
--to=jgg@nvidia.com \
--cc=aharonl@nvidia.com \
--cc=dledford@redhat.com \
--cc=leon@kernel.org \
--cc=leonro@nvidia.com \
--cc=linux-rdma@vger.kernel.org \
--cc=maorg@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=saeedm@nvidia.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