From: Steve Wise <swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
To: dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org
Cc: linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH v3 0/3] iw_cxgb4 fixes for 4.14-rc
Date: Fri, 15 Sep 2017 14:27:07 -0700 [thread overview]
Message-ID: <cover.1505510827.git.swise@opengridcomputing.com> (raw)
v2 didn't make it to the email list, so I'm sending v3. I'm having a
bad day...
---
Hey Doug, please consider these bug fixes for 4.14-rc. I'm resending
a "v2" series which overrides the first submission, and the "RESEND"
submission.
Changes since "RESEND"
- fixed up the commit comment for patch 3
Chances since original submission
- Move the stable tag to the correct location in the commit log
Thanks,
Steve.
---
Steve Wise (3):
iw_cxgb4: put ep reference in pass_accept_req()
iw_cxgb4: drop listen destroy replies if no ep found
iw_cxgb4: remove the stid on listen create failure
drivers/infiniband/hw/cxgb4/cm.c | 9 +++++++--
1 file changed, 7 insertions(+), 2 deletions(-)
--
1.8.3.1
--
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
next reply other threads:[~2017-09-15 21:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-15 21:27 Steve Wise [this message]
[not found] ` <cover.1505510827.git.swise-7bPotxP6k4+P2YhJcF5u+vpXobYPEAuW@public.gmane.org>
2017-09-05 18:52 ` [PATCH v3 2/3] iw_cxgb4: drop listen destroy replies if no ep found Steve Wise
2017-09-05 18:52 ` [PATCH v3 3/3] iw_cxgb4: remove the stid on listen create failure Steve Wise
2017-09-13 16:52 ` [PATCH v3 1/3] iw_cxgb4: put ep reference in pass_accept_req() Steve Wise
2017-09-22 17:01 ` [PATCH v3 0/3] iw_cxgb4 fixes for 4.14-rc Doug Ledford
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=cover.1505510827.git.swise@opengridcomputing.com \
--to=swise-7bpotxp6k4+p2yhjcf5u+vpxobypeauw@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@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;
as well as URLs for NNTP newsgroup(s).