From: Lijun Ou <oulijun-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
To: dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
jgg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org
Cc: leon-DgEjT+Ai2ygdnm+yROfE0A@public.gmane.org,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: [PATCH V2 for-next 0/3] Several fixes for hns
Date: Wed, 7 Feb 2018 17:49:27 +0800 [thread overview]
Message-ID: <1517996970-79496-1-git-send-email-oulijun@huawei.com> (raw)
This patchset include three fixes for hns driver. the first patch
mainly matched with IB protocol. the second patch fix the bug
with freeing memory by __get_free_pages. the last patch mainly
fix the bug when changed the hw mac address.
Change from V1:
1. Fix the comment given by Jason Gunthorpe
Lijun Ou (2):
RDMA/hns: Fix a bug with modifying mac address
RDMA/hns: Use free_pages function instead of free_page
Yixian Liu (1):
RDMA/hns: Fix QP state judgement before receiving work requests
drivers/infiniband/hw/hns/hns_roce_hw_v2.c | 2 +-
drivers/infiniband/hw/hns/hns_roce_main.c | 3 ++-
drivers/infiniband/hw/hns/hns_roce_mr.c | 2 +-
3 files changed, 4 insertions(+), 3 deletions(-)
--
1.9.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:[~2018-02-07 9:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 9:49 Lijun Ou [this message]
[not found] ` <1517996970-79496-1-git-send-email-oulijun-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2018-02-07 9:49 ` [PATCH V2 for-next 1/3] RDMA/hns: Fix a bug with modifying mac address Lijun Ou
2018-02-07 9:49 ` [PATCH V2 for-next 2/3] RDMA/hns: Fix QP state judgement before receiving work requests Lijun Ou
2018-02-07 9:49 ` [PATCH V2 for-next 3/3] RDMA/hns: Use free_pages function instead of free_page Lijun Ou
2018-02-14 23:53 ` [PATCH V2 for-next 0/3] Several fixes for hns 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=1517996970-79496-1-git-send-email-oulijun@huawei.com \
--to=oulijun-hv44wf8li93qt0dzr+alfa@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=jgg-VPRAkNaXOzVWk0Htik3J/w@public.gmane.org \
--cc=leon-DgEjT+Ai2ygdnm+yROfE0A@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).