DPDK patches and discussions
 help / color / mirror / Atom feed
From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Zaheer R M <zaheer.rm@globaledgesoft.com>,
	Supriya Shekhar Mane <sm.supriya@globaledgesoft.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: Chandrakant Sharpa <s.chandrakant@globaledgesoft.com>,
	Gurusidhesh G H <gurusidhesh.gh@globaledgesoft.com>,
	Stephen Hemminger <stephen@networkplumber.org>,
	Thomas Monjalon <thomas@monjalon.net>,
	David Marchand <david.marchand@redhat.com>
Subject: Re: [dpdk-dev] New PMD integration to next version release
Date: Tue, 4 May 2021 09:41:44 +0100	[thread overview]
Message-ID: <79b47a57-704e-44f9-faf0-0973ebfb47da@intel.com> (raw)
In-Reply-To: <HK2PR03MB4308A61F39B9FB4CC56DAC06835B9@HK2PR03MB4308.apcprd03.prod.outlook.com>

On 5/3/2021 1:17 PM, Zaheer R M wrote:
> Hello “DPDK Community”,
> 
> We are glad to inform you that we have developed 3 PMDs using DPDK version 19.11.3
> 
> One of our premium customer has sponsored to develop DPDK-Ethernet-PMD using WPJ419 Compex Platform and is willing to Contribute to DPDK community.
> WPJ419 board uses “Qualcomm Chipset -- Dakota”. There are several commercially available AP / routers based on this platform.
> PMD we have developed has successfully completed “Beta Release” and we want to contribute as is to DPDK community.
> We are ready with our changes and willing to contribute asap. Further releases shall be submitted in the form of patches.
> 
> We are planning to integrate DPDK-Ethernet-PMD to DPDK community in next stable release 19.11.9 i.e. by June 2021.
> We have learnt that “A meeting happens at https://meet.jit.si/DPDK every two weeks” to discuss new topic.
> Requesting “Technical Board” to add “DPDK-Ethernet-PMD for WPJ419 platform” topic in the agenda and notify scheduled meeting date and time.
> 

Hi Supriya and Zaheer,

Great to hear that you are willing to upstream your driver.

There is no need to discuss this in any meeting, although you are welcome to
attend both meetings (both are open to public). All you need to do is send your
patches to the dev mailing list.

As Stephen highlighted, the new features are added to the regular releases, not
to the stable trees, so first thing you need to do is backport it to the regular
release.
We are about to close the v21.05, so next release can be v21.08.


It would be nice if you can send your roadmap update for v21.08, you can find
multiple samples in the mail list, to indicate your intention to add your driver
for v21.08.

And please check the contribution guide documentation, it should have enough
details on how to contribute, expected coding conventions and checks etc..
https://doc.dpdk.org/guides/contributing/index.html

Thanks,
ferruh

> With thanks and regards,
> Zaheer RM
> 
> From: Supriya Shekhar Mane <sm.supriya@globaledgesoft.com>
> Sent: Monday, May 3, 2021 4:01 PM
> To: dev@dpdk.org
> Cc: Chandrakant Sharpa <s.chandrakant@globaledgesoft.com>; Zaheer R M <zaheer.rm@globaledgesoft.com>
> Subject: New PMD integration to next version release
> 
> Hi Maintainers,
> 
> We want to open source the Dakota Ethernet PMD.
> We are ready with changes to be open source.
> We want to integrate our changes onto the next release: 19.11.9
> Kindly, guide us with the process and initiation of the same.
> 
> Regards,
> Supriya Mane
> 
> Disclaimer: "This message is intended only for the designated recipient(s). It may contain confidential or proprietary information and may be subject to other confidentiality protections. If you are not a designated recipient, you may not review, copy or distribute this message. Please notify the sender by e-mail and delete this message. GlobalEdge does not accept any liability for virus infected mails."
> 


  reply	other threads:[~2021-05-04  8:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-03 10:30 Supriya Shekhar Mane
2021-05-03 12:17 ` Zaheer R M
2021-05-04  8:41   ` Ferruh Yigit [this message]
2021-05-03 16:33 ` Stephen Hemminger

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=79b47a57-704e-44f9-faf0-0973ebfb47da@intel.com \
    --to=ferruh.yigit@intel.com \
    --cc=david.marchand@redhat.com \
    --cc=dev@dpdk.org \
    --cc=gurusidhesh.gh@globaledgesoft.com \
    --cc=s.chandrakant@globaledgesoft.com \
    --cc=sm.supriya@globaledgesoft.com \
    --cc=stephen@networkplumber.org \
    --cc=thomas@monjalon.net \
    --cc=zaheer.rm@globaledgesoft.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).