DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Kumar, Ravi1" <Ravi1.Kumar@amd.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Cc: "Giriyapura,
	Maheshwaramurthy" <Maheshwaramurthy.Giriyapura@amd.com>,
	"Somalapuram, Amaranath" <Amaranath.Somalapuram@amd.com>,
	"Jayakumar, Tamil-Velan" <Tamil-Velan.Jayakumar@amd.com>
Subject: [dpdk-dev] Pushing feature patches to DPDK stable release
Date: Fri, 28 Feb 2020 10:46:31 +0000	[thread overview]
Message-ID: <MW2PR12MB2570890D3330D59358D73BA2AEE80@MW2PR12MB2570.namprd12.prod.outlook.com> (raw)

[AMD Official Use Only - Internal Distribution Only]

Hi,

I want to understand details on DPDK mainline process.

Is it possible to upstream patches to the older stable branches, upstreaming to 18.11 as an example? How do we do it?

Regards,
Ravi



             reply	other threads:[~2020-02-28 10:46 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-28 10:46 Kumar, Ravi1 [this message]
2020-02-28 11:18 ` Kevin Traynor
2020-03-15 17:35   ` Kumar, Ravi1

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=MW2PR12MB2570890D3330D59358D73BA2AEE80@MW2PR12MB2570.namprd12.prod.outlook.com \
    --to=ravi1.kumar@amd.com \
    --cc=Amaranath.Somalapuram@amd.com \
    --cc=Maheshwaramurthy.Giriyapura@amd.com \
    --cc=Tamil-Velan.Jayakumar@amd.com \
    --cc=dev@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).