From: "Kumar, Ravi1" <Ravi1.Kumar@amd.com>
To: Kevin Traynor <ktraynor@redhat.com>, "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>,
Luca Boccassi <bluca@debian.org>
Subject: Re: [dpdk-dev] Pushing feature patches to DPDK stable release
Date: Sun, 15 Mar 2020 17:35:50 +0000 [thread overview]
Message-ID: <DM6PR12MB29878A004B2E9C94E7DEB13CAEF80@DM6PR12MB2987.namprd12.prod.outlook.com> (raw)
In-Reply-To: <05c05ccf-0605-bf1d-0555-3036689ede79@redhat.com>
[AMD Public Use]
Hi Traynor,
Thank you very much for the detailed explanation. It clears all our doubts.
Regards,
Ravi
>
>-----Original Message-----
>From: Kevin Traynor <ktraynor@redhat.com>
>Sent: Friday, February 28, 2020 4:49 PM
>To: Kumar, Ravi1 <Ravi1.Kumar@amd.com>; dev@dpdk.org
>Cc: Giriyapura, Maheshwaramurthy <Maheshwaramurthy.Giriyapura@amd.com>; Somalapuram, Amaranath <Amaranath.Somalapuram@amd.com>; Jayakumar, Tamil-Velan <Tamil-Velan.Jayakumar@amd.com>; Luca Boccassi <bluca@debian.org>
>Subject: Re: [dpdk-dev] Pushing feature patches to DPDK stable release
>
>[CAUTION: External Email]
>
>On 28/02/2020 10:46, Kumar, Ravi1 wrote:
>> [AMD Official Use Only - Internal Distribution Only]
>>
>> Hi,
>>
>
>Hi Ravi,
>
>Please remove the banner above, it is not appropriate for an open source mailing list.
My apologies. The banner is a new automatic update in the Outlook and I missed it.
>
>> 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?
>>
>
>There is information about the stable releases and what is backported
>here: https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdoc.dpdk.org%2Fguides%2Fcontributing%2Fstable.html&data=02%7C01%7Cravi1.kumar%40amd.com%7C42a97cd3ed4943fa042908d7bc3ffa04%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637184855288300009&sdata=IV3Z7bMKpRR24GEphhYMrUBtNUJUpBA9kUolQeELMS4%3D&reserved=0
>
>(I have an outstanding todo to expand these docs a bit)
>
>fyi - Luca and I did a presentation in September about DPDK LTS where we touched on this also: https://nam11.safelinks.protection.outlook.com/?url=https%3A%2F%2Fyoutu.be%2F6ipOgMhkpU4&data=02%7C01%7Cravi1.kumar%40amd.com%7C42a97cd3ed4943fa042908d7bc3ffa04%7C3dd8961fe4884e608e11a82d994e183d%7C0%7C0%7C637184855288300009&sdata=lesi83xytT78AyJ4ONUS7zLn5lTZ0gWioPvYQYFgr1Q%3D&reserved=0
>
>thanks,
>Kevin.
>
>> Regards,
>> Ravi
>>
>>
>
prev parent reply other threads:[~2020-03-15 17:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 10:46 Kumar, Ravi1
2020-02-28 11:18 ` Kevin Traynor
2020-03-15 17:35 ` Kumar, Ravi1 [this message]
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=DM6PR12MB29878A004B2E9C94E7DEB13CAEF80@DM6PR12MB2987.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=bluca@debian.org \
--cc=dev@dpdk.org \
--cc=ktraynor@redhat.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).