From: Tiwei Bie <tiwei.bie@intel.com>
To: Hideyuki Yamashita <yamashita.hideyuki@po.ntt-tx.co.jp>
Cc: "Burakov, Anatoly" <anatoly.burakov@intel.com>,
dev@dpdk.org, Yasufumi Ogawa <ogawa.yasufumi@lab.ntt.co.jp>,
Nakamura Hioryuki <nakamura.hiroyuki@po.ntt-tx.co.jp>,
maxime.coquelin@redhat.com, zhihong.wang@intel.com
Subject: Re: [dpdk-dev] rte_eal_hotplug_remove() generates error message
Date: Wed, 2 Jan 2019 17:19:00 +0800 [thread overview]
Message-ID: <20190102091900.GA12203@dpdk-tbie.sh.intel.com> (raw)
In-Reply-To: <201812270554.wBR5rnsV005042@ccmail04.silk.ntt-tx.co.jp>
On Thu, Dec 27, 2018 at 02:52:17PM +0900, Hideyuki Yamashita wrote:
> Q1.
> I CCed my patch to stable@dpdk.org
> Is that mean it will be reflected into 18.11 stable release?
Yes.
> The reason why I ask this is I think it is better that bug should
> be reflected into LTS because I and SPP users mainly use DPDK LTS(18.11).
>
> Q2.
> If yes, when will those stable release will be released?
> (e.g. once a month )
Plans can be found here:
https://core.dpdk.org/roadmap/#stable
>
> Q3.
> I understand my patch is acked and merged into
> dpdk-next-virtio.
> What is dpdk-next-virtio?
> It is the branch which will be reflected into next release?
It's already in main repo now:
http://git.dpdk.org/dpdk/commit/drivers/net/vhost?id=6e3339ca07734e59cd0c24594e3014ab49a0ffc0
prev parent reply other threads:[~2019-01-02 9:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-09 4:30 [dpdk-dev] dpdk vlan strip offload bug for I350 nic? 1534898891
2018-12-09 5:23 ` =?gb18030?B?MTUzNDg5ODg5MQ==?=
2018-12-18 2:26 ` Zhao1, Wei
2018-12-10 7:53 ` [dpdk-dev] rte_eal_hotplug_remove() generates error message Hideyuki Yamashita
2018-12-11 0:54 ` Hideyuki Yamashita
2018-12-17 10:02 ` Hideyuki Yamashita
2018-12-17 10:23 ` Burakov, Anatoly
2018-12-17 10:38 ` Burakov, Anatoly
2018-12-17 11:03 ` Hideyuki Yamashita
2018-12-17 10:45 ` Hideyuki Yamashita
2018-12-17 11:21 ` Burakov, Anatoly
2018-12-17 12:10 ` Hideyuki Yamashita
2018-12-18 2:39 ` Tiwei Bie
2018-12-18 3:11 ` Hideyuki Yamashita
2018-12-18 5:12 ` Tiwei Bie
2018-12-18 5:52 ` Hideyuki Yamashita
2018-12-18 6:25 ` Tiwei Bie
2018-12-18 11:30 ` Hideyuki Yamashita
2018-12-18 13:09 ` Tiwei Bie
2018-12-27 5:52 ` Hideyuki Yamashita
2019-01-02 9:19 ` Tiwei Bie [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=20190102091900.GA12203@dpdk-tbie.sh.intel.com \
--to=tiwei.bie@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=maxime.coquelin@redhat.com \
--cc=nakamura.hiroyuki@po.ntt-tx.co.jp \
--cc=ogawa.yasufumi@lab.ntt.co.jp \
--cc=yamashita.hideyuki@po.ntt-tx.co.jp \
--cc=zhihong.wang@intel.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).