From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [PATCH] bnxt: Add Cumulus+ PCI ID
Date: Mon, 27 Jun 2016 09:41:00 +0100
Message-ID: <20160627084059.GA19588@bricha3-MOBL3>
References: <1466546300-44716-1-git-send-email-ajit.khaparde@broadcom.com>
 <20160624115934.GJ13456@bricha3-MOBL3>
 <CACZ4nht8hUvHZjdcWsb2FVe92g-ihU432MLHOJq3+-FW0rq3pw@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Cc: dev@dpdk.org, Stephen Hurd <stephen.hurd@broadcom.com>
To: Ajit Khaparde <ajit.khaparde@broadcom.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mga02.intel.com (mga02.intel.com [134.134.136.20])
 by dpdk.org (Postfix) with ESMTP id 71CC05A83
 for <dev@dpdk.org>; Mon, 27 Jun 2016 10:41:04 +0200 (CEST)
Content-Disposition: inline
In-Reply-To: <CACZ4nht8hUvHZjdcWsb2FVe92g-ihU432MLHOJq3+-FW0rq3pw@mail.gmail.com>
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On Fri, Jun 24, 2016 at 01:31:37PM -0500, Ajit Khaparde wrote:
> On Fri, Jun 24, 2016 at 6:59 AM, Bruce Richardson <
> bruce.richardson@intel.com> wrote:
>=20
> > On Tue, Jun 21, 2016 at 04:58:20PM -0500, Ajit Khaparde wrote:
> > > This patch adds support for Cumulus+ Ethernet adapters.
> > > These Cumulus+ Ethernet adapters support 10Gb/25Gb/40Gb/50Gb speeds=
.
> > >
> > > Signed-off-by: Ajit Khaparde <ajit.khaparde@broadcom.com>
> >
> > Applied to dpdk-next-net/rel_16_07
> >
> =E2=80=8BThanks Bruce. At what point in time will the changes under rel=
_16_07
> be available in the dpdk tree?
> git://dpdk.org/dpdk
>=20
That's more a question for Thomas than for me, since he is the one who pu=
lls
next-net into the mainline. However, from discussions with Thomas, it sho=
uld be
fairly soon, hopefully today or tomorrow.

/Bruce