DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Olga Shern <olgas@mellanox.com>
Cc: Thomas Monjalon <thomas.monjalon@6wind.com>,
	Vincent JARDIN <vincent.jardin@6wind.com>,
	Jerin Jacob <jerin.jacob@caviumnetworks.com>,
	Olivier Matz <olivier.matz@6wind.com>,
	Liming Sun <lsun@mellanox.com>, Yael Shenhav <yaeli@mellanox.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	Chris Metcalf <cmetcalf@mellanox.com>
Subject: Re: [dpdk-dev] [PATCH 0/4] catch up TILE-Gx support in DPDK
Date: Tue, 21 Feb 2017 09:14:04 +0000	[thread overview]
Message-ID: <20170221091404.GA190772@bricha3-MOBL3.ger.corp.intel.com> (raw)
In-Reply-To: <DB6PR0501MB2757CB36AF49BB9A071C0904D35E0@DB6PR0501MB2757.eurprd05.prod.outlook.com>

On Mon, Feb 20, 2017 at 08:24:43PM +0000, Olga Shern wrote:
> Hi Thomas,  All
> 
> Mellanox agrees to remove TILE-Gx support from DPDK.org, but will continue to support customers using DPDK. 
> Customer that needs support should contact Mellanox directly.
> 
> Best Regards,
> Olga
>
Thank you for the clear response. It's a big help to the project for
moving forward, rather than just waiting for an answer that may never
come.

Regards,
/Bruce

  reply	other threads:[~2017-02-21  9:14 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-18  1:52 Chris Metcalf
2017-02-18  1:52 ` [dpdk-dev] [PATCH 1/4] tile: avoid use of non-upstreamed <arch/cycle.h> Chris Metcalf
2017-02-18  1:52 ` [dpdk-dev] [PATCH 2/4] tile: remove requirement for <arch/mpipe_{xaui, gbe}_def.h headers Chris Metcalf
2017-02-18  1:52 ` [dpdk-dev] [PATCH 3/4] strict alignment: generalize warning handling Chris Metcalf
2017-02-18  1:52 ` [dpdk-dev] [PATCH 4/4] tile: fix remaining build issues Chris Metcalf
2017-02-18  9:29 ` [dpdk-dev] [PATCH 0/4] catch up TILE-Gx support in DPDK Thomas Monjalon
2017-02-20 20:24   ` Olga Shern
2017-02-21  9:14     ` Bruce Richardson [this message]
2017-02-21 15:54   ` Liming Sun
2017-02-21 18:15     ` Chris Metcalf
2017-02-27 15:36 ` 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=20170221091404.GA190772@bricha3-MOBL3.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=cmetcalf@mellanox.com \
    --cc=dev@dpdk.org \
    --cc=jerin.jacob@caviumnetworks.com \
    --cc=lsun@mellanox.com \
    --cc=olgas@mellanox.com \
    --cc=olivier.matz@6wind.com \
    --cc=thomas.monjalon@6wind.com \
    --cc=vincent.jardin@6wind.com \
    --cc=yaeli@mellanox.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).