Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1400982 > unrolled thread

Re: [RESEND PATCH v7 00/21] Add HiSilicon RoCE driver

Started byDoug Ledford <dledford@redhat.com>
First post2016-05-13 23:10 +0200
Last post2016-05-23 03:10 +0200
Articles 2 — 2 participants

Back to article view | Back to linux.kernel

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.


Contents

  Re: [RESEND PATCH v7 00/21] Add HiSilicon RoCE driver Doug Ledford <dledford@redhat.com> - 2016-05-13 23:10 +0200
    Re: [RESEND PATCH v7 00/21] Add HiSilicon RoCE driver "Wei Hu (Xavier)" <xavier.huwei@huawei.com> - 2016-05-23 03:10 +0200

#1400982 — Re: [RESEND PATCH v7 00/21] Add HiSilicon RoCE driver

FromDoug Ledford <dledford@redhat.com>
Date2016-05-13 23:10 +0200
SubjectRe: [RESEND PATCH v7 00/21] Add HiSilicon RoCE driver
Message-ID<rysvp-2VC-11@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

On 05/09/2016 11:04 PM, Lijun Ou wrote:
> The HiSilicon Network Substem is a long term evolution IP which is
> supposed to be used in HiSilicon ICT SoCs. HNS (HiSilicon Network
> Sybsystem) also has a hardware support of performing RDMA with
> RoCEE.
> The driver for HiSilicon RoCEE(RoCE Engine) is a platform driver and
> will support mulitple versions of SOCs in future. This version of driver
> is meant to support Hip06 SoC(which confirms to RoCEEv1 hardware
> specifications).
> 
> Changes v6 -> v7:
> 1. modify some type of parameter, use bool replace the original type.
> 2. add the Signed-off-by signatures in the first patch.
> 3. delete the improper print sentence in hns_roce_create_eq.

One thing you should be aware of (but which you may not care about,
which is fine) is that if you want your driver to be available as part
of the OpenFabric Alliances OFED distribution, the license on the files
would need to be "GPL or BSD" (see the remainder of the RDMA stack for
examples).  If you don't want that license on your files, I'm fine with
that, and I won't hold up your submission based on the license.  If,
however, you *do* want your code to be shipable as part of OFED, it is
much easier to update the license on the files before you submit them
and third parties modify them.  If you want to change the license later,
you have to get every person that has made any substantive change to the
file to agree to the license change.


-- 
Doug Ledford <dledford@redhat.com>
              GPG KeyID: 0E572FDD


[toc] | [next] | [standalone]


#1405059

From"Wei Hu (Xavier)" <xavier.huwei@huawei.com>
Date2016-05-23 03:10 +0200
Message-ID<rBMxz-7Na-3@gated-at.bofh.it>
In reply to#1400982
Hi, Doug Ledford

We will modify the license description of the beginning of the code file 
in  patch v8.
Thanks

Regards
Wei Hu

On 2016/5/14 5:09, Doug Ledford wrote:
> On 05/09/2016 11:04 PM, Lijun Ou wrote:
>> The HiSilicon Network Substem is a long term evolution IP which is
>> supposed to be used in HiSilicon ICT SoCs. HNS (HiSilicon Network
>> Sybsystem) also has a hardware support of performing RDMA with
>> RoCEE.
>> The driver for HiSilicon RoCEE(RoCE Engine) is a platform driver and
>> will support mulitple versions of SOCs in future. This version of driver
>> is meant to support Hip06 SoC(which confirms to RoCEEv1 hardware
>> specifications).
>>
>> Changes v6 -> v7:
>> 1. modify some type of parameter, use bool replace the original type.
>> 2. add the Signed-off-by signatures in the first patch.
>> 3. delete the improper print sentence in hns_roce_create_eq.
> One thing you should be aware of (but which you may not care about,
> which is fine) is that if you want your driver to be available as part
> of the OpenFabric Alliances OFED distribution, the license on the files
> would need to be "GPL or BSD" (see the remainder of the RDMA stack for
> examples).  If you don't want that license on your files, I'm fine with
> that, and I won't hold up your submission based on the license.  If,
> however, you *do* want your code to be shipable as part of OFED, it is
> much easier to update the license on the files before you submit them
> and third parties modify them.  If you want to change the license later,
> you have to get every person that has made any substantive change to the
> file to agree to the license change.
>
>

[toc] | [prev] | [standalone]


Back to top | Article view | linux.kernel


csiph-web