From: Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: Dennis Dalessandro
<dennis.dalessandro-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Cc: Mike Marciniszyn
<mike.marciniszyn-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Jan Sokolowski
<jan.sokolowski-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Kaike Wan <kaike.wan-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
"Michael J. Ruhl"
<michael.j.ruhl-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>,
Kamenee Arumugam
<kamenee.arumugam-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
Subject: Re: [PATCH for-next 0/9] IB/hfi1, qib, rdmavt: patches for next 08/28/2017
Date: Mon, 28 Aug 2017 19:31:58 -0400 [thread overview]
Message-ID: <1503963118.52034.13.camel@redhat.com> (raw)
In-Reply-To: <20170828182121.29434.18989.stgit-9QXIwq+3FY+1XWohqUldA0EOCMrvLtNR@public.gmane.org>
On Mon, 2017-08-28 at 11:23 -0700, Dennis Dalessandro wrote:
> Hi Doug,
>
> Here is the next round of patches for our drivers. There are a few
> patches from
> Mike that adds a qp iterator and starts the work of cleaning up some
> of our code
> that needs to walk qps. The rest are minor bug fixes.
>
> Patches can can also be found in my GitHub repo at:
> https://github.com/ddalessa/kernel/tree/for-4.14
Thanks, series applied.
--
Doug Ledford <dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
GPG KeyID: B826A3330E572FDD
Key fingerprint = AE6B 1BDA 122B 23B4 265B 1274 B826 A333 0E57 2FDD
--
To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2017-08-28 23:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-28 18:23 [PATCH for-next 0/9] IB/hfi1, qib, rdmavt: patches for next 08/28/2017 Dennis Dalessandro
[not found] ` <20170828182121.29434.18989.stgit-9QXIwq+3FY+1XWohqUldA0EOCMrvLtNR@public.gmane.org>
2017-08-28 18:23 ` [PATCH for-next 1/9] IB/hfi1: Acquire QSFP cable information on loopback Dennis Dalessandro
2017-08-28 18:23 ` [PATCH for-next 2/9] IB/hif1: Remove static tracing from SDMA hot path Dennis Dalessandro
2017-08-28 18:23 ` [PATCH for-next 3/9] IB/qib: Stricter bounds checking for copy to buffer Dennis Dalessandro
2017-08-28 18:23 ` [PATCH for-next 4/9] IB/hfi1: Use accessor to determine ring size Dennis Dalessandro
2017-08-28 18:23 ` [PATCH for-next 5/9] IB/rdmavt: Add QP iterator API for QPs Dennis Dalessandro
2017-08-28 18:23 ` [PATCH for-next 6/9] IB/hfi1: Convert hfi1_error_port_qps() to use new QP iterator Dennis Dalessandro
2017-08-28 18:23 ` [PATCH for-next 7/9] IB/hfi1: Convert qp_stats debugfs interface to use new iterator API Dennis Dalessandro
2017-08-28 18:24 ` [PATCH for-next 8/9] IB/qib: " Dennis Dalessandro
2017-08-28 18:24 ` [PATCH for-next 9/9] IB/rdmavt: Handle dereg of inuse MRs properly Dennis Dalessandro
2017-08-28 23:31 ` 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=1503963118.52034.13.camel@redhat.com \
--to=dledford-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
--cc=dennis.dalessandro-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=jan.sokolowski-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=kaike.wan-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=kamenee.arumugam-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=michael.j.ruhl-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=mike.marciniszyn-ral2JQCrhuEAvxtiuMwx3w@public.gmane.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