linux-rdma.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dennis Dalessandro <dennis.dalessandro@intel.com>
To: Doug Ledford <dledford@redhat.com>, jgg@ziepe.ca
Cc: Mike Marciniszyn <mike.marciniszyn@intel.com>,
	linux-rdma@vger.kernel.org, Alex Estrin <alex.estrin@intel.com>,
	stable@vger.kernel.org, Kaike Wan <kaike.wan@intel.com>,
	"Michael J. Ruhl" <michael.j.ruhl@intel.com>,
	Don Dutile <ddutile@redhat.com>,
	Kamenee Arumugam <kamenee.arumugam@intel.com>
Subject: Re: [PATCH for-next 0/5] IB/hfi1,isert: Updates for-next 5/15/2018
Date: Tue, 22 May 2018 20:54:05 -0400	[thread overview]
Message-ID: <77a63b1c-1307-8533-4a34-b46768627f46@intel.com> (raw)
In-Reply-To: <38faf50391a9bc1a8d874a32ce5857a4023dff3e.camel@redhat.com>

On 5/22/2018 3:33 PM, Doug Ledford wrote:
> On Tue, 2018-05-15 at 18:31 -0700, Dennis Dalessandro wrote:
>> Hi Doug and Jason,
>>
>> Here are some patches to go to for-next. One is a code cleanup. The rest are
>> bug fixes that are probably not serious enough for an -rc6. The one that may be
>> on the fence is the isert patch. Since it only affects debug kernels it can
>> probably even wait till for-next. It has been marked stable though.
>>
>> ---
>>
>> Alex Estrin (1):
>>        IB/isert: Fix for lib/dma_debug check_sync warning
>>
>> Kamenee Arumugam (1):
>>        IB/Hfi1: Mask Unsupported Request error bit in PCIe AER
>>
>> Michael J. Ruhl (1):
>>        IB/hfi1: Set port number for errorinfo MAD response
>>
>> Mike Marciniszyn (2):
>>        IB/hfi1: Cleanup of exp_rcv
>>        IB/{rdmavt,hfi1}; Change hrtimer add to use the pinned variation
> 
> Hi Denny,
> 
> I dropped the PCI bit fiddling patch as per comments.  Please provide a
> more detailed commit message if you want this patch to go in.

Kamenee is looking into this some more. Yeah, OK to drop for now, we'll 
resubmit with at least a better commit message or a different approach 
depending on her investigation.
  > I provided my own guestimate of a commit message touchup to the hrtimers
> patch.  Please let me know if I was wrong in my assumptions there.

Sounds good to me, thanks!

-Denny

      reply	other threads:[~2018-05-23  0:54 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-16  1:31 [PATCH for-next 0/5] IB/hfi1,isert: Updates for-next 5/15/2018 Dennis Dalessandro
2018-05-16  1:31 ` [PATCH for-next 5/5] IB/isert: Fix for lib/dma_debug check_sync warning Dennis Dalessandro
2018-05-16 20:04   ` Jason Gunthorpe
2018-05-16 21:03     ` Don Dutile
2018-05-17 15:03     ` Dennis Dalessandro
2018-05-17 15:10       ` Jason Gunthorpe
2018-05-17 23:01         ` Don Dutile
2018-05-18  9:00           ` Christoph Hellwig
2018-05-18 17:50             ` Don Dutile
2018-05-22 19:33 ` [PATCH for-next 0/5] IB/hfi1,isert: Updates for-next 5/15/2018 Doug Ledford
2018-05-23  0:54   ` Dennis Dalessandro [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=77a63b1c-1307-8533-4a34-b46768627f46@intel.com \
    --to=dennis.dalessandro@intel.com \
    --cc=alex.estrin@intel.com \
    --cc=ddutile@redhat.com \
    --cc=dledford@redhat.com \
    --cc=jgg@ziepe.ca \
    --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).