From: Leon Romanovsky <leon@leon.nu>
To: oulijun <oulijun@huawei.com>
Cc: dledford@redhat.com, sean.hefty@intel.com,
hal.rosenstock@gmail.com, davem@davemloft.net,
jeffrey.t.kirsher@intel.com, jiri@mellanox.com,
ogerlitz@mellanox.com, linux-rdma@vger.kernel.org,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
gongyangming@huawei.com, xiaokun@huawei.com,
tangchaofei@huawei.com, haifeng.wei@huawei.com,
yisen.zhuang@huawei.com, yankejian@huawei.com,
lisheng011@huawei.com, charles.chenxin@huawei.com,
linuxarm@huawei.com
Subject: Re: [RESEND PATCH V4 2/3] IB/hns: Add HiSilicon RoCE driver support
Date: Tue, 5 Apr 2016 18:32:03 +0300 [thread overview]
Message-ID: <20160405153203.GJ5264@leon.nu> (raw)
In-Reply-To: <57036A25.9000106@huawei.com>
On Tue, Apr 05, 2016 at 03:32:53PM +0800, oulijun wrote:
> >> .../infiniband/hw/hisilicon/hns/hns_roce_v1_hw.c | 2832 ++++++++++++++++++++
> >> .../infiniband/hw/hisilicon/hns/hns_roce_v1_hw.h | 985 +++++++
> > ^^^^^^
> > Do you support v1 of RoCE or v1 of your HW?
> >
> Here, v1 stands for hw, that is, we support v1 of our hw.
So you should write hns_roce_hw_v1 and not hns_roce_v1_hw
> >> 23 files changed, 10429 insertions(+)
> >
> > Please appreciate the effort needed to review such large patch and
> > invest time and effort to divide this to number of small easy review patches.
> >
> Surely, i have pay attention to the patch, but i consider that it is not better to
> split the patch into small patch. because it will the base function of RoCE.
> For your advice, i will make further efforts to taking a discussion how to reslove the question.
Faisal Latif's submission [1] can help you to get inspiration.
Also please DON'T submit your patches till you get rid of unrelated
functions/macros/defines and DMA operations for register access.
[1] https://lwn.net/Articles/668721/
>
> thanks
> Lijun Ou
> > .
> >
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-rdma" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2016-04-05 15:32 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-01 9:21 [RESEND PATCH V4 0/3] IB/hns: Add HiSilicon RoCE driver Lijun Ou
2016-04-01 9:21 ` [RESEND PATCH V4 1/3] net: hns: Add reset function support for " Lijun Ou
2016-04-01 9:21 ` [RESEND PATCH V4 2/3] IB/hns: Add HiSilicon RoCE driver support Lijun Ou
[not found] ` <1459502492-19891-3-git-send-email-oulijun-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2016-04-02 1:58 ` Leon Romanovsky
[not found] ` <20160402015830.GD8565-2ukJVAZIZ/Y@public.gmane.org>
2016-04-05 7:32 ` oulijun
2016-04-05 15:32 ` Leon Romanovsky [this message]
2016-04-01 9:21 ` [RESEND PATCH V4 3/3] IB/hns: Add binding document for HiSilicon RoCE driver Lijun Ou
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=20160405153203.GJ5264@leon.nu \
--to=leon@leon.nu \
--cc=charles.chenxin@huawei.com \
--cc=davem@davemloft.net \
--cc=dledford@redhat.com \
--cc=gongyangming@huawei.com \
--cc=haifeng.wei@huawei.com \
--cc=hal.rosenstock@gmail.com \
--cc=jeffrey.t.kirsher@intel.com \
--cc=jiri@mellanox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=lisheng011@huawei.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=oulijun@huawei.com \
--cc=sean.hefty@intel.com \
--cc=tangchaofei@huawei.com \
--cc=xiaokun@huawei.com \
--cc=yankejian@huawei.com \
--cc=yisen.zhuang@huawei.com \
/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).