stable.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Doug Ledford <dledford@redhat.com>
To: Dennis Dalessandro <dennis.dalessandro@intel.com>
Cc: Mike Marciniszyn <mike.marciniszyn@intel.com>,
	linux-rdma@vger.kernel.org, stable@vger.kernel.org,
	Kaike Wan <kaike.wan@intel.com>,
	"Michael J. Ruhl" <michael.j.ruhl@intel.com>,
	Grzegorz Morys <grzegorz.morys@intel.com>,
	Harish Chegondi <harish.chegondi@intel.com>,
	Kamenee Arumugam <kamenee.arumugam@intel.com>
Subject: Re: [PATCH for-next 00/16] IB/hfi1, qib, rdmavt: patches for next 08/21/2017
Date: Mon, 28 Aug 2017 19:16:22 -0400	[thread overview]
Message-ID: <1503962182.52034.7.camel@redhat.com> (raw)
In-Reply-To: <20170822011657.32701.22207.stgit@scvm10.sc.intel.com>

On Mon, 2017-08-21 at 18:26 -0700, Dennis Dalessandro wrote:
> Hi Doug,
> 
> Another week another set of patches. I meant to send on Friday but
> was waiting
> for 0-day builds to complete. I still haven't gotten any
> notification, the
> service may be down but I wanted to get these on the list anyway for
> review.
> If I get any bad result I will reply but there is nothing
> particularly scary
> in here.
> 
> Content wise this is more clean ups including a patch for rdmavt to
> use
> the put_swqe/clear_mr_ref helpers that support was added for in
> qib/hfi1
> previously. 
> 
> We have some minor bug fixes as well. A large portion of the patch
> set is
> a clean up/refactoring exercise by Harish that I took because it
> makes the code
> cleaner and easier to read.
> 
> Note, one of the fixes from Mike is marked stable. I don't know if
> it's something
> that you want to take into this late of an RC so it may be best to
> just go to
> next and flow through the stable process.
> 
> Patches can can also be found in my GitHub repo at:
> https://github.com/ddalessa/kernel/tree/for-4.14
> 

Hi Denny, 

I went ahead and took these, but please make sure you follow up with
the review requests from Leon.  Preferably by the time I'm back from
PTO the incremental patches will be waiting for me ;-)

-- 
Doug Ledford <dledford@redhat.com>
    GPG KeyID: B826A3330E572FDD
    Key fingerprint = AE6B 1BDA 122B 23B4 265B  1274 B826 A333 0E57 2FDD

      parent reply	other threads:[~2017-08-28 23:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-22  1:26 [PATCH for-next 00/16] IB/hfi1, qib, rdmavt: patches for next 08/21/2017 Dennis Dalessandro
2017-08-22  1:26 ` [PATCH for-next 02/16] IB/{qib, hfi1}: Avoid flow control testing for RDMA write operation Dennis Dalessandro
2017-08-28 23:16 ` Doug Ledford [this message]

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=1503962182.52034.7.camel@redhat.com \
    --to=dledford@redhat.com \
    --cc=dennis.dalessandro@intel.com \
    --cc=grzegorz.morys@intel.com \
    --cc=harish.chegondi@intel.com \
    --cc=kaike.wan@intel.com \
    --cc=kamenee.arumugam@intel.com \
    --cc=linux-rdma@vger.kernel.org \
    --cc=michael.j.ruhl@intel.com \
    --cc=mike.marciniszyn@intel.com \
    --cc=stable@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).