From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: "Shippen, Greg" <Greg.Shippen@amd.com>,
"Kumar, Ravi1" <Ravi1.Kumar@amd.com>,
Thomas Monjalon <thomas@monjalon.net>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH 3/4] doc: Add documents for AMD XGBE Ethernet
Date: Wed, 15 Nov 2017 00:07:48 +0000 [thread overview]
Message-ID: <AM2PR04MB0753B7BDAEFE3FA4426AE94D89290@AM2PR04MB0753.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <DM2PR12MB0138AA6F2C7782A949E2521C9D280@DM2PR12MB0138.namprd12.prod.outlook.com>
HI Greg,
There is no restriction on sending the code to DPDK for public review and it is up to the respective maintainers to provide comments.
However, your patches can not be merged to DPDK and it's next trees till the Licensing issues are sorted out.
Regards,
Hemant
> -----Original Message-----
> From: Shippen, Greg [mailto:Greg.Shippen@amd.com]
> Sent: Tuesday, November 14, 2017 3:16 PM
> To: Kumar, Ravi1 <Ravi1.Kumar@amd.com>; Thomas Monjalon
> <thomas@monjalon.net>
> Cc: dev@dpdk.org; Hemant Agrawal <hemant.agrawal@nxp.com>
> Subject: RE: [dpdk-dev] [PATCH 3/4] doc: Add documents for AMD XGBE
> Ethernet
>
> Hement:
>
> I'd like to understand whether we can get dpdk.org some early code for
> review in parallel with our efforts to resolve the licensing issue. To answer
> this question, I need to understand what happens if we sent you v2 before
> the end of the month? Is the code visible to all dpdk.org and the public or
> just to internal reviewers?
>
> Greg
>
> -----Original Message-----
> From: Kumar, Ravi1
> Sent: Tuesday, November 14, 2017 12:36 AM
> To: Thomas Monjalon <thomas@monjalon.net>
> Cc: dev@dpdk.org; Hemant Agrawal <hemant.agrawal@nxp.com>; Shippen,
> Greg <Greg.Shippen@amd.com>
> Subject: RE: [dpdk-dev] [PATCH 3/4] doc: Add documents for AMD XGBE
> Ethernet
>
> >15/09/2017 14:26, Kumar, Ravi1:
> >
> >> >1. As a non-written convention, we are adding following statement in
> >> >the top of such dual licensed files : " This file is provided under
> >> >a dual
> >> >BSD/GPLv2 license. When using or redistributing this file, you may do
> so under either license.". And license header as "BSD LICENSE" or "GPL .."
> >> >
> >> >2. you are using a modified version of BSD. Typical license in DPDK files
> are BSD-3 or BSD-2. If you intend to use your specific version of BSD license,
> it will require TechBoard, Gov Board and legal approval.
> >> >
> >> >3. Additionally your BSD license is including a proprietary license text of
> Synopsys. This will also need approval before it get included in DPDK.
> >> >
> >> >4. It seems you have copy pasted the same license text in all the files.
> >> >e.g. do you intend to keep dual license option + Synopsys text for your
> documentation and the files, which you have created originally for dpdk
> only.
> >> >
> >>
> >> Hi Hemant,
> >>
> >> Thank you very much for the detailed explanation. We have to work with
> our Legal team on this. We will get back to you.
> >
> >Please keep us posted about your legal issues.
> >Maybe there is something we can help.
> >
> >If you target 18.02, I suggest to send a v2 before the end of the month, in
> order to give us time to review what else must be reworked.
> >
> >Thanks
>
> Thanks for following up on this.
>
> The AMD legal team is working with Synopsys legal team on this as both
> the companies licenses are involved. Thats why it is taking longer than
> expected.
> We are working hard to meet the month end deadline and want to target
> 18.02.
>
> Regards,
> Ravi
next prev parent reply other threads:[~2017-11-15 0:07 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-13 17:47 [dpdk-dev] [PATCH 1/4] Add AMD XGBE Ethernet config support in DPDK Ravi Kumar
2017-09-13 17:47 ` [dpdk-dev] [PATCH 2/4] net/axgbe : Add PMD support for AMD XGBE Ethernet Ravi Kumar
2017-09-14 16:25 ` Ferruh Yigit
2017-09-15 12:29 ` Kumar, Ravi1
2017-09-13 17:47 ` [dpdk-dev] [PATCH 3/4] doc: Add documents " Ravi Kumar
2017-09-14 11:57 ` Hemant Agrawal
2017-09-14 14:02 ` Kumar, Ravi1
2017-09-15 4:41 ` Hemant Agrawal
2017-09-15 12:26 ` Kumar, Ravi1
2017-11-13 19:20 ` Thomas Monjalon
2017-11-14 6:36 ` Kumar, Ravi1
[not found] ` <DM2PR12MB0138AA6F2C7782A949E2521C9D280@DM2PR12MB0138.namprd12.prod.outlook.com>
2017-11-15 0:07 ` Hemant Agrawal [this message]
2017-11-17 17:48 ` Shippen, Greg
2017-11-19 16:09 ` Hemant Agrawal
2017-09-14 16:26 ` Ferruh Yigit
2017-09-18 17:39 ` Mcnamara, John
2017-09-13 17:47 ` [dpdk-dev] [PATCH 4/4] maintainers: add maintainer for AMD AXGBE PMD Ravi Kumar
2017-09-14 16:26 ` Ferruh Yigit
2017-09-14 8:53 ` [dpdk-dev] [PATCH 1/4] Add AMD XGBE Ethernet config support in DPDK Ferruh Yigit
2017-09-14 9:48 ` Kumar, Ravi1
2017-09-14 16:25 ` Ferruh Yigit
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=AM2PR04MB0753B7BDAEFE3FA4426AE94D89290@AM2PR04MB0753.eurprd04.prod.outlook.com \
--to=hemant.agrawal@nxp.com \
--cc=Greg.Shippen@amd.com \
--cc=Ravi1.Kumar@amd.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).