DPDK website maintenance
 help / color / mirror / Atom feed
From: "Du, Frank" <frank.du@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
	Nathan Southern <nsouthern@linuxfoundation.org>
Cc: "web@dpdk.org" <web@dpdk.org>,
	"Richardson, Bruce" <bruce.richardson@intel.com>,
	"Yu, Ping" <ping.yu@intel.com>
Subject: RE: addition to Ecosystem Page of DPDK Website
Date: Thu, 10 Nov 2022 01:11:07 +0000	[thread overview]
Message-ID: <SJ0PR11MB478312C5849585E874D239EF80019@SJ0PR11MB4783.namprd11.prod.outlook.com> (raw)
In-Reply-To: <10172299.U7f9L36N0a@thomas>

Hi Thomas,

Yes, it's our target also, we want to upstream all patches. Ex, for https://github.com/OpenVisualCloud/Media-Transport-Library/blob/main/patches/dpdk/22.07/hdr_split/0001-ethdev-introduce-protocol-header-API.patch, it was already upstream in this commit https://github.com/DPDK/dpdk/commit/629dad3ef325f9b4519d94c29ec49b77b386d850, but it is still in our patch list since we are using 22.07. Indeed we has some patches which still in POC stage are not in upstreaming process now, but finally all local patches will take the way to upstream I think.

Thanks,
Frank

-----Original Message-----
From: Thomas Monjalon <thomas@monjalon.net> 
Sent: Thursday, November 10, 2022 3:56 AM
To: Nathan Southern <nsouthern@linuxfoundation.org>
Cc: web@dpdk.org; Richardson, Bruce <bruce.richardson@intel.com>; Du, Frank <frank.du@intel.com>
Subject: Re: addition to Ecosystem Page of DPDK Website

02/11/2022 23:25, Nathan Southern:
> Hello,
> 
> We need this project added to the dpdk.org ecosystem page.
> 
> https://github.com/OpenVisualCloud/Media-Transport-Library

It looks OK to add,
with the hope that the directory for their DPDK patches will reduce over time.
We should encourage project to avoid keeping non-upstreamed patches.
Do we know whether all patches were submitted to DPDK?



  reply	other threads:[~2022-11-14 22:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02 22:25 Nathan Southern
2022-11-09 19:55 ` Thomas Monjalon
2022-11-10  1:11   ` Du, Frank [this message]
2022-11-10  7:36     ` Thomas Monjalon
2022-11-24  2:14       ` Du, Frank
2022-11-28  9:12         ` Yu, Ping
2022-11-28 22:38           ` Thomas Monjalon

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=SJ0PR11MB478312C5849585E874D239EF80019@SJ0PR11MB4783.namprd11.prod.outlook.com \
    --to=frank.du@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=nsouthern@linuxfoundation.org \
    --cc=ping.yu@intel.com \
    --cc=thomas@monjalon.net \
    --cc=web@dpdk.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).