From: Dennis Dalessandro <dennis.dalessandro@intel.com>
To: jgg@ziepe.ca, dledford@redhat.com
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH for-next v2 00/11] rdmavt/hfi1 updates for next
Date: Wed, 11 Dec 2019 08:34:40 -0500 [thread overview]
Message-ID: <3a570d5b-330b-bbc6-9a7a-60a112b1c66b@intel.com> (raw)
In-Reply-To: <20191126141055.58836.79452.stgit@awfm-01.aw.intel.com>
On 11/26/2019 9:12 AM, Dennis Dalessandro wrote:
> Here are some refactoring and code reorg patches for the merge window. Nothing
> too scary, no new features. This lays the ground work for stuff coming in
> future merge cycles.
>
> There is also one bug fix, from Kaike.
>
> Changes from v1
> ---------------
> Fix Review-by tags with corrupted email address.
>
> ---
>
> Grzegorz Andrejczuk (3):
> IB/hfi1: Move common receive IRQ code to function
> IB/hfi1: Decouple IRQ name from type
> IB/hfi1: Return void in packet receiving functions
>
> Kaike Wan (1):
> IB/hfi1: Don't cancel unused work item
>
> Michael J. Ruhl (1):
> IB/hfi1: List all receive contexts from debugfs
>
> Mike Marciniszyn (6):
> IB/hfi1: Add accessor API routines to access context members
> IB/hfi1: Move chip specific functions to chip.c
> IB/hfi1: Add fast and slow handlers for receive context
> IB/hfi1: IB/hfi1: Add an API to handle special case drop
> IB/hfi1: Create API for auto activate
> IB/rdmavt: Correct comments in rdmavt_qp.h header
I guess these didn't catch the train for 5.5 merge window. Do I need to
resubmit to break this into two series, one for RC and one for next?
I think 1, 9, 10, and 11 could/should probably go for RC.
-Denny
next prev parent reply other threads:[~2019-12-11 13:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 14:12 [PATCH for-next v2 00/11] rdmavt/hfi1 updates for next Dennis Dalessandro
2019-11-26 14:12 ` [PATCH for-next v2 01/11] IB/hfi1: Add accessor API routines to access context members Dennis Dalessandro
2019-11-26 14:12 ` [PATCH for-next v2 02/11] IB/hfi1: List all receive contexts from debugfs Dennis Dalessandro
2019-12-02 13:30 ` Ruhl, Michael J
2019-12-05 13:49 ` [PATCH for-next v3] " Dennis Dalessandro
2020-01-03 19:48 ` Jason Gunthorpe
2019-11-26 14:12 ` [PATCH for-next v2 03/11] IB/hfi1: Move chip specific functions to chip.c Dennis Dalessandro
2019-11-26 14:12 ` [PATCH for-next v2 04/11] IB/hfi1: Add fast and slow handlers for receive context Dennis Dalessandro
2019-11-26 14:12 ` [PATCH for-next v2 05/11] IB/hfi1: Move common receive IRQ code to function Dennis Dalessandro
2019-11-26 14:12 ` [PATCH for-next v2 06/11] IB/hfi1: IB/hfi1: Add an API to handle special case drop Dennis Dalessandro
2019-11-26 14:12 ` [PATCH for-next v2 07/11] IB/hfi1: Create API for auto activate Dennis Dalessandro
2019-11-26 14:12 ` [PATCH for-next v2 08/11] IB/hfi1: Decouple IRQ name from type Dennis Dalessandro
2019-11-26 14:13 ` [PATCH for-next v2 09/11] IB/hfi1: Return void in packet receiving functions Dennis Dalessandro
2019-11-26 14:13 ` [PATCH for-next v2 10/11] IB/rdmavt: Correct comments in rdmavt_qp.h header Dennis Dalessandro
2019-11-26 14:13 ` [PATCH for-next v2 11/11] IB/hfi1: Don't cancel unused work item Dennis Dalessandro
2019-11-26 15:31 ` [PATCH for-next v2 00/11] rdmavt/hfi1 updates for next Jason Gunthorpe
2019-12-11 13:34 ` Dennis Dalessandro [this message]
2019-12-11 16:21 ` Jason Gunthorpe
2019-12-11 16:33 ` 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=3a570d5b-330b-bbc6-9a7a-60a112b1c66b@intel.com \
--to=dennis.dalessandro@intel.com \
--cc=dledford@redhat.com \
--cc=jgg@ziepe.ca \
--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;
as well as URLs for NNTP newsgroup(s).