From: Olivier Matz <olivier.matz@6wind.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Cc: Thomas Monjalon <thomas.monjalon@6wind.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
Zhigang Lu <zlu@ezchip.com>, Liming Sun <lsun@ezchip.com>,
dev@dpdk.org, olgas@mellanox.com
Subject: Re: [dpdk-dev] [PATCH] doc: announce TILE-Gx removal
Date: Tue, 14 Feb 2017 12:03:04 +0100 [thread overview]
Message-ID: <20170214120304.26b66a5a@platinum> (raw)
In-Reply-To: <20170214105019.GA31008@bricha3-MOBL3.ger.corp.intel.com>
On Tue, 14 Feb 2017 10:50:19 +0000, Bruce Richardson
<bruce.richardson@intel.com> wrote:
> On Tue, Feb 14, 2017 at 10:28:39AM +0100, Thomas Monjalon wrote:
> > 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?
> >
>
> Regretfully, I must agree with Thomas on this. In the absense of a
> response from someone to maintain this, it should be removed.
>
> Acked-by: Bruce Richardson <bruce.richardson@intel.com>
>
Same here.
Acked-by: Olivier Matz <olivier.matz@6wind.com>
next prev parent reply other threads:[~2017-02-14 11:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-13 10:52 Thomas Monjalon
2017-02-14 8:50 ` Mcnamara, John
2017-02-14 8:58 ` Thomas Monjalon
2017-02-14 9:28 ` Thomas Monjalon
2017-02-14 10:50 ` Bruce Richardson
2017-02-14 10:56 ` Jerin Jacob
2017-02-14 11:03 ` Olivier Matz [this message]
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 ` [dpdk-dev] " 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=20170214120304.26b66a5a@platinum \
--to=olivier.matz@6wind.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=lsun@ezchip.com \
--cc=olgas@mellanox.com \
--cc=thomas.monjalon@6wind.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 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).