From: "Mcnamara, John" <john.mcnamara@intel.com>
To: "Richardson, Bruce" <bruce.richardson@intel.com>
Cc: Thomas Monjalon <thomas.monjalon@6wind.com>,
Zhigang Lu <zlu@ezchip.com>, Liming Sun <lsun@ezchip.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] doc: announce TILE-Gx removal
Date: Tue, 14 Feb 2017 11:51:01 +0000 [thread overview]
Message-ID: <B27915DBBA3421428155699D51E4CFE2026CBE13@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <20170214112512.GA28908@bricha3-MOBL3.ger.corp.intel.com>
> -----Original Message-----
> From: Richardson, Bruce
> Sent: Tuesday, February 14, 2017 11:25 AM
> To: Mcnamara, John <john.mcnamara@intel.com>
> Cc: Thomas Monjalon <thomas.monjalon@6wind.com>; Zhigang Lu
> <zlu@ezchip.com>; Liming Sun <lsun@ezchip.com>; dev@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH] doc: announce TILE-Gx removal
>
> On Tue, Feb 14, 2017 at 08:50:07AM +0000, Mcnamara, John wrote:
> >
> >
> > > -----Original Message-----
> > > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Thomas Monjalon
> > > Sent: Monday, February 13, 2017 10:53 AM
> > > To: Zhigang Lu <zlu@ezchip.com>; Liming Sun <lsun@ezchip.com>
> > > Cc: dev@dpdk.org
> > > Subject: [dpdk-dev] [PATCH] doc: announce TILE-Gx removal
> > >
> > > Signed-off-by: Thomas Monjalon <thomas.monjalon@6wind.com>
> > > ---
> > > doc/guides/rel_notes/deprecation.rst | 3 +++
> > > 1 file changed, 3 insertions(+)
> > >
> > > diff --git a/doc/guides/rel_notes/deprecation.rst
> > > b/doc/guides/rel_notes/deprecation.rst
> > > index b49e0a0..d40b137 100644
> > > --- a/doc/guides/rel_notes/deprecation.rst
> > > +++ b/doc/guides/rel_notes/deprecation.rst
> > > @@ -62,3 +62,6 @@ Deprecation Notices
> > > PMDs that implement the latter.
> > > Target release for removal of the legacy API will be defined once
> most
> > > PMDs have switched to rte_flow.
> > > +
> > > +* The architecture TILE-Gx and the associated mpipe driver are not
> > > + maintained and will be removed in 17.05.
> >
> > The notification should probably be for removal in 17.08, to one release
> cycle to respond/fix/update.
> >
> > It would also be good to hear from EZChip/Mellanox on this.
> >
> > John
>
> If - as seems likely - this deprecation notice makes it into the 17.02
> release, I would just ask that the actual removal of the code *not* take
> place at the start of the 17.05 release cycle, to be sure to give further
> additional grace period for someone to respond to this. I think it is only
> fair to wait till just before the RC's are produced to remove the code,
> given it is such a drastic step, and the official notice of removal is
> only inserted right before 17.02 goes out.
>
Hi,
That seems like a fair compromise.
John
next prev parent reply other threads:[~2017-02-14 11:51 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
2017-02-14 13:34 ` Maxime Coquelin
2017-02-14 11:25 ` Bruce Richardson
2017-02-14 11:51 ` Mcnamara, John [this message]
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=B27915DBBA3421428155699D51E4CFE2026CBE13@IRSMSX103.ger.corp.intel.com \
--to=john.mcnamara@intel.com \
--cc=bruce.richardson@intel.com \
--cc=dev@dpdk.org \
--cc=lsun@ezchip.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).