From: Dennis Dalessandro <dennis.dalessandro@cornelisnetworks.com>
To: Jason Gunthorpe <jgg@nvidia.com>, Leon Romanovsky <leon@kernel.org>
Cc: Dean Luick <dean.luick@cornelisnetworks.com>, linux-rdma@vger.kernel.org
Subject: Re: [PATCH for-next 0/7] FIXME and other fixes
Date: Fri, 20 Jan 2023 12:50:35 -0500 [thread overview]
Message-ID: <a830a1f2-0042-4fc6-7416-da8a8d2d1fe6@cornelisnetworks.com> (raw)
In-Reply-To: <Y8rSiD5s+ZFV666t@nvidia.com>
On 1/20/23 12:42 PM, Jason Gunthorpe wrote:
> On Fri, Jan 20, 2023 at 07:09:43PM +0200, Leon Romanovsky wrote:
>
>> Backmerge will cause to the situation where features are brought to -rc.
>> The cherry-pick will be:
>> 1. Revert [PATCH for-next 2/7] IB/hfi1: Assign npages earlier] from -next
>> 2. Apply [PATCH for-next 2/7] IB/hfi1: Assign npages earlier] to -rc
>
> You don't need to revert, we just need to merge a RC release to -next
> and deal with the conflict, if any.
Thanks this sounds like a good way to go.
-Denny
next prev parent reply other threads:[~2023-01-20 17:50 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 [this message]
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=a830a1f2-0042-4fc6-7416-da8a8d2d1fe6@cornelisnetworks.com \
--to=dennis.dalessandro@cornelisnetworks.com \
--cc=dean.luick@cornelisnetworks.com \
--cc=jgg@nvidia.com \
--cc=leon@kernel.org \
--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