From: Jason Gunthorpe <jgg@ziepe.ca>
To: Dennis Dalessandro <dennis.dalessandro@intel.com>
Cc: dledford@redhat.com, linux-rdma@vger.kernel.org
Subject: Re: [PATCH for-rc 0/4] Patches for 5.5 rc
Date: Fri, 20 Dec 2019 09:47:46 -0400 [thread overview]
Message-ID: <20191220134746.GD13506@ziepe.ca> (raw)
In-Reply-To: <20191219211609.58387.86077.stgit@awfm-01.aw.intel.com>
On Thu, Dec 19, 2019 at 04:19:15PM -0500, Dennis Dalessandro wrote:
> The first two patches I wouldn't ordinarily have sent for -rc but I noticed we
> did this in the previous -rc post, add an API because we use it in the next fix.
> That's what the first two patches here do. It's understandable if you are
> skeptical that those are OK for -rc and in which case you can drop and we can
> send for next.
The only one that looks RC worthy to me is:
> Kaike Wan (1):
> IB/hfi1: Don't cancel unused work item
>
> Mike Marciniszyn (2):
> IB/hfi1: Add accessor API routines to access context members
> IB/rdmavt: Correct comments in rdmavt_qp.h header
How is correcting comments a needed fix?
Jason
next prev parent reply other threads:[~2019-12-20 13:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-19 21:19 [PATCH for-rc 0/4] Patches for 5.5 rc Dennis Dalessandro
2019-12-19 21:19 ` [PATCH for-rc 1/4] IB/hfi1: Add accessor API routines to access context members Dennis Dalessandro
2019-12-19 21:19 ` [PATCH for-rc 2/4] IB/hfi1: List all receive contexts from debugfs Dennis Dalessandro
2019-12-19 21:19 ` [PATCH for-rc 3/4] IB/rdmavt: Correct comments in rdmavt_qp.h header Dennis Dalessandro
2019-12-19 21:19 ` [PATCH for-rc 4/4] IB/hfi1: Don't cancel unused work item Dennis Dalessandro
2019-12-20 13:47 ` Jason Gunthorpe [this message]
2020-01-03 20:47 ` [PATCH for-rc 0/4] Patches for 5.5 rc Jason Gunthorpe
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=20191220134746.GD13506@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=dennis.dalessandro@intel.com \
--cc=dledford@redhat.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;
as well as URLs for NNTP newsgroup(s).