From: Jason Gunthorpe <jgg-uk2M96/98Pc@public.gmane.org>
To: "Wei Hu (Xavier)" <xavier.huwei-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Cc: dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org,
linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
xavier.huwei-WVlzvzqoTvw@public.gmane.org,
xavier_huwei-9Onoh4P/yGk@public.gmane.org,
linuxarm-hv44wF8Li93QT0dZR+AlfA@public.gmane.org
Subject: Re: [PATCH 0/3] RDMA/hns: Bug fixes in hns RoCE driver
Date: Mon, 27 Nov 2017 11:36:37 -0700 [thread overview]
Message-ID: <20171127183637.GA13966@ziepe.ca> (raw)
In-Reply-To: <1511750484-102395-1-git-send-email-xavier.huwei-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
On Mon, Nov 27, 2017 at 10:41:21AM +0800, Wei Hu (Xavier) wrote:
> This patch-set introduces three patches to fix about the memory
> related issues.
If these patches are for-rc can you revise the commit message to more
clearly explain what the bug is, and supply Fixes lines?
Otherwise these will go to 4.16
It looks like the first one is for-rc material as it looks like DMA
will fail sometimes if the smmu is enabled?
The other two are less clear to me - is this just fixing the code to
conform to the DMA API, or is there an actual real user-impacting bug here?
Thanks
Jason
--
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 prev parent reply other threads:[~2017-11-27 18:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-27 2:41 [PATCH 0/3] RDMA/hns: Bug fixes in hns RoCE driver Wei Hu (Xavier)
2017-11-27 2:41 ` [PATCH 1/3] RDMA/hns: Fix the issue of IOVA not page continuous in hip08 Wei Hu (Xavier)
2017-11-27 2:41 ` [PATCH 2/3] RDMA/hns: Get rid of virt_to_page and vmap calls after dma_alloc_coherent Wei Hu (Xavier)
2017-11-27 2:41 ` [PATCH 3/3] RDMA/hns: Get rid of page operation " Wei Hu (Xavier)
[not found] ` <1511750484-102395-1-git-send-email-xavier.huwei-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2017-11-27 18:36 ` Jason Gunthorpe [this message]
[not found] ` <20171127183637.GA13966-uk2M96/98Pc@public.gmane.org>
2017-11-28 6:15 ` [PATCH 0/3] RDMA/hns: Bug fixes in hns RoCE driver Leon Romanovsky
2017-11-28 13:20 ` Dennis Dalessandro
2017-11-28 18:39 ` Jason Gunthorpe
[not found] ` <20171128183910.GA21325-uk2M96/98Pc@public.gmane.org>
2017-11-28 18:50 ` Bart Van Assche
[not found] ` <1511895042.28512.6.camel-Sjgp3cTcYWE@public.gmane.org>
2017-11-28 19:08 ` Leon Romanovsky
2017-11-28 19:33 ` Jason Gunthorpe
[not found] ` <20171128193311.GB21325-uk2M96/98Pc@public.gmane.org>
2017-11-28 20:27 ` Dennis Dalessandro
[not found] ` <c3d23cf8-ed10-73a3-7b5b-8c58b7aa4781-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2017-11-29 10:00 ` Jonathan Cameron
2017-11-28 6:28 ` Wei Hu (Xavier)
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=20171127183637.GA13966@ziepe.ca \
--to=jgg-uk2m96/98pc@public.gmane.org \
--cc=dledford-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-rdma-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linuxarm-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=xavier.huwei-WVlzvzqoTvw@public.gmane.org \
--cc=xavier.huwei-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
--cc=xavier_huwei-9Onoh4P/yGk@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).