From: Leon Romanovsky <leon@kernel.org>
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: Wed, 1 Feb 2023 10:40:17 +0200 [thread overview]
Message-ID: <Y9olcZ7PWIzc6BqS@unreal> (raw)
In-Reply-To: <cc1c9687-9537-b514-29e0-4fc764d93b09@cornelisnetworks.com>
On Tue, Jan 31, 2023 at 11:57:22AM -0500, Dennis Dalessandro wrote:
> On 1/31/23 9:58 AM, Jason Gunthorpe wrote:
> > On Mon, Jan 30, 2023 at 04:57:56PM -0500, Dennis Dalessandro wrote:
> >
> >> I didn't see this make it out yet. Can this still make it in for -rc? Based on
> >> Jason's reply [1] sounds like it will just work itself out in for-next.
> >>
> >> [1] https://lore.kernel.org/linux-rdma/Y8rSiD5s+ZFV666t@nvidia.com/
> >
> > Well, it looks OK to me, you should do a test merge yourself and
> > confirm nothing got mangled
>
> I tested this last week by cherry picking:
>
> a479433a6b7a ("IB/hfi1: Assign npages earlier")
>
> onto for-rc, then merged for-rc into for-next. Looks ok. No conflicts.
Jason took this patch to his wip/jgg-for-rc branch.
Thanks
>
> -Denny
next prev parent reply other threads:[~2023-02-01 8:40 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
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 [this message]
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=Y9olcZ7PWIzc6BqS@unreal \
--to=leon@kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox