All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ye Xiaolong <xiaolong.ye@intel.com>
To: Hideyuki Yamashita <yamashita.hideyuki@ntt-tx.co.jp>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] which is the code base when submitting patch around end of September
Date: Fri, 9 Aug 2019 10:40:02 +0800	[thread overview]
Message-ID: <20190809024002.GA85810@intel.com> (raw)
In-Reply-To: <20190809111910.D110.17218CA3@ntt-tx.co.jp_1>

Hi,

On 08/09, Hideyuki Yamashita wrote:
>Hello Experts,
>
>
>Very basic question to create patch.
>
>I am planning to post patch set which introduce new functionality (not
>bug fix ).
>Note that I will post the patch set on end of September.

If your patch is targeted for 19.11 release, you need to send out your V1 patch
before proposal deadline 9/6, you can check the roadmap in http://core.dpdk.org/roadmap/.

>
>Q1. 
>If I post patch set to dev-ml, which is the code base?
>Source code which is retrieved from "git clone" ?
>Or tar ball of previous version like "dpdk-19.05.tar.gz"?
>

In most of cases, you should clone the main tree (git clone http://dpdk.org/git/dpdk)  
as the code base, and regularly rebase your patchset if you have new versions.

>Q2. 
>If review of the patch starts around October, when 
>will the patch will be merged, if patch is good one.
>19.11 LTS? or 20.02?
>(Are there any rule or deadlines?)

yes, please refer to the deadlines in the roadmap page.

Thanks,
Xiaolong

>
>Thanks in advance,
>Hideyuki Yamashita
>NTT TechnoCross
>

  reply	other threads:[~2019-08-09  2:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-08  8:12 [dpdk-dev] 19.11 Intel Roadmap O'Driscoll, Tim
2019-08-09  2:19 ` [dpdk-dev] which is the code base when submitting patch around end of September Hideyuki Yamashita
2019-08-09  2:40   ` Ye Xiaolong [this message]
2019-08-09  2:52     ` Hideyuki Yamashita

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=20190809024002.GA85810@intel.com \
    --to=xiaolong.ye@intel.com \
    --cc=dev@dpdk.org \
    --cc=yamashita.hideyuki@ntt-tx.co.jp \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.