From: Jason Gunthorpe <jgg@nvidia.com>
To: Saeed Mahameed <saeed@kernel.org>
Cc: Leon Romanovsky <leon@kernel.org>,
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>
Subject: Re: [PATCH rdma-next 0/2] Real time/free running timestamp support
Date: Fri, 12 Feb 2021 17:14:08 -0400 [thread overview]
Message-ID: <20210212211408.GA1860468@nvidia.com> (raw)
In-Reply-To: <5d4731e2394049ca66012f82e1645bdec51aca78.camel@kernel.org>
On Fri, Feb 12, 2021 at 01:09:20PM -0800, Saeed Mahameed wrote:
> On Fri, 2021-02-12 at 14:10 -0400, Jason Gunthorpe wrote:
> > 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
> >
>
> mmm, i was planing to resubmit this patch with the netdev real time
> support series, since the uplink representor is getting delayed, I
> thought I could submit the real time stuff today. can you wait on the
> ifc patch, i will re-send it today if you will, but it must go through
> the shared branch
Friday of rc7 is a bit late to be sending new patches for the first
time, isn't it??
But sure, if you update the shared branch right now I'll fix up rdma.git
Jason
next prev parent reply other threads:[~2021-02-12 21:15 UTC|newest]
Thread overview: 13+ 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-12 18:10 ` [PATCH rdma-next 0/2] Real time/free running timestamp support Jason Gunthorpe
2021-02-12 21:09 ` Saeed Mahameed
2021-02-12 21:14 ` Jason Gunthorpe [this message]
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=20210212211408.GA1860468@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=saeed@kernel.org \
/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).