DPDK patches and discussions
 help / color / mirror / Atom feed
From: Hideyuki Yamashita <yamashita.hideyuki@ntt-tx.co.jp>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: [dpdk-dev] which is the code base when submitting patch around end of September
Date: Fri, 09 Aug 2019 11:19:10 +0900	[thread overview]
Message-ID: <20190809111910.D110.17218CA3@ntt-tx.co.jp_1> (raw)
In-Reply-To: <26FA93C7ED1EAA44AB77D62FBE1D27BAB790C9E0@IRSMSX108.ger.corp.intel.com>

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.

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"?

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?)

Thanks in advance,
Hideyuki Yamashita
NTT TechnoCross


  reply	other threads:[~2019-08-09  2:19 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 ` Hideyuki Yamashita [this message]
2019-08-09  2:40   ` [dpdk-dev] which is the code base when submitting patch around end of September Ye Xiaolong
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=20190809111910.D110.17218CA3@ntt-tx.co.jp_1 \
    --to=yamashita.hideyuki@ntt-tx.co.jp \
    --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).