From: Leon Romanovsky <leonro@nvidia.com>
To: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
Cc: Jason Gunthorpe <jgg@nvidia.com>,
Dean Luick <dean.luick@cornelisnetworks.com>,
<linux-rdma@vger.kernel.org>
Subject: Re: [PATCH for-next 0/7] FIXME and other fixes
Date: Sun, 15 Jan 2023 13:46:39 +0200 [thread overview]
Message-ID: <Y8Pnn8NokWNsKQO/@unreal> (raw)
In-Reply-To: <bce1ab36-66e4-465c-e051-94e397d108ba@cornelisnetworks.com>
On Fri, Jan 13, 2023 at 12:21:50PM -0500, Dennis Dalessandro wrote:
> On 1/10/23 4:03 PM, Dennis Dalessandro wrote:
> > On 1/10/23 9:58 AM, Jason Gunthorpe wrote:
> >> On Mon, Jan 09, 2023 at 02:03:58PM -0500, Dennis Dalessandro wrote:
> >>> Dean fixes the FIXME that was left by Jason in the code to use the interval
> >>> notifier.
> >>
> >> ? Which patch did that?
> >
> > My fault. The last patch in the previous series [1] was meant to go first here.
> > I got off by 1 when I was splitting the patches out for submit.
> >
> > [1]
> > https://lore.kernel.org/linux-rdma/167328549178.1472310.9867497376936699488.stgit@awfm-02.cornelisnetworks.com/T/#u
>
> As a side effect of this, can we pull patch 2/7 from this series into the RC?
No, everything is in for-rc/for-next now.
Thanks
next prev parent reply other threads:[~2023-01-15 11:47 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 19:03 [PATCH for-next 0/7] FIXME and other fixes Dennis Dalessandro
2023-01-09 19:04 ` [PATCH for-next 1/7] IB/hfi1: Remove redundant pageidx variable Dennis Dalessandro
2023-01-09 19:04 ` [PATCH for-next 2/7] IB/hfi1: Assign npages earlier Dennis Dalessandro
2023-01-09 19:04 ` [PATCH for-next 3/7] IB/hfi1: Consolidate the creation of user TIDs Dennis Dalessandro
2023-01-09 19:04 ` [PATCH for-next 4/7] IB/hfi1: Improve TID validity checking Dennis Dalessandro
2023-01-09 19:04 ` [PATCH for-next 5/7] IB/hfi1: Split IB counter allocation Dennis Dalessandro
2023-01-09 19:04 ` [PATCH for-next 6/7] IBh/hfi1: Update RMT size calculation Dennis Dalessandro
2023-01-09 19:04 ` [PATCH for-next 7/7] IB/hfi1: Use dma_mmap_coherent for matching buffers Dennis Dalessandro
2023-01-10 10:53 ` [PATCH for-next 0/7] FIXME and other fixes Leon Romanovsky
2023-01-10 14:58 ` Jason Gunthorpe
2023-01-10 21:03 ` Dennis Dalessandro
2023-01-13 17:21 ` Dennis Dalessandro
2023-01-15 11:46 ` Leon Romanovsky [this message]
2023-01-16 5:36 ` Dennis Dalessandro
2023-01-16 7:16 ` Leon Romanovsky
2023-01-18 13:04 ` Dennis Dalessandro
2023-01-20 17:09 ` Leon Romanovsky
2023-01-20 17:42 ` Jason Gunthorpe
2023-01-20 17:50 ` Dennis Dalessandro
2023-01-22 9:14 ` Leon Romanovsky
2023-01-23 16:49 ` Dennis Dalessandro
2023-01-30 21:57 ` Dennis Dalessandro
2023-01-31 14:58 ` Jason Gunthorpe
2023-01-31 16:57 ` Dennis Dalessandro
2023-02-01 8:40 ` Leon Romanovsky
2023-02-02 15:56 ` Dennis Dalessandro
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=Y8Pnn8NokWNsKQO/@unreal \
--to=leonro@nvidia.com \
--cc=dean.luick@cornelisnetworks.com \
--cc=dennis.dalessandro@cornelisnetworks.com \
--cc=jgg@nvidia.com \
--cc=linux-rdma@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.