From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Mcnamara, John" <john.mcnamara@intel.com>
Cc: Zhigang Lu <zlu@ezchip.com>, Liming Sun <lsun@ezchip.com>,
dev@dpdk.org, olgas@mellanox.com
Subject: Re: [PATCH] doc: announce TILE-Gx removal
Date: Tue, 14 Feb 2017 10:28:39 +0100 [thread overview]
Message-ID: <7089891.d7DOEDsTKe@xps13> (raw)
In-Reply-To: <1588932.Whvs7BuFal@xps13>
2017-02-14 09:58, Thomas Monjalon:
> 2017-02-14 08:50, Mcnamara, John:
> > The notification should probably be for removal in 17.08, to one release cycle to respond/fix/update.
>
> There were some previous messages/warnings and there were no answer.
> I have asked a working free toolchain, I did not have it.
> We have asked some questions about drivers support, no reply.
> I have asked about removal, no reply.
> I really do not see why we should keep it longer.
Some public links:
Recent warnings: http://dpdk.org/ml/archives/dev/2017-February/056981.html
Recent patch from Jerin without any comment: http://dpdk.org/commit/dff9071
Bug in 16.04 without any comment: https://mail-archive.com/dev@dpdk.org/msg31596.html
Work stopped in March, last year: https://mail-archive.com/dev@dpdk.org/msg43536.html
No update for free toolchain: https://mail-archive.com/dev@dpdk.org/msg42651.html
One year without any news is enough.
Hope it convinces you.
> > It would also be good to hear from EZChip/Mellanox on this.
>
> They are mute since a long time on this topic.
> Olga, do you confirm?
next prev parent reply other threads:[~2017-02-14 9:28 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 10:52 [PATCH] doc: announce TILE-Gx removal Thomas Monjalon
2017-02-14 8:50 ` Mcnamara, John
2017-02-14 8:58 ` Thomas Monjalon
2017-02-14 9:28 ` Thomas Monjalon [this message]
2017-02-14 10:50 ` Bruce Richardson
2017-02-14 10:56 ` Jerin Jacob
2017-02-14 11:03 ` Olivier Matz
2017-02-14 13:34 ` Maxime Coquelin
2017-02-14 11:25 ` Bruce Richardson
2017-02-14 11:51 ` Mcnamara, John
2017-02-14 18:38 ` Thomas Monjalon
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=7089891.d7DOEDsTKe@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=lsun@ezchip.com \
--cc=olgas@mellanox.com \
--cc=zlu@ezchip.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 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.