From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?UTF-8?Q?Jan_M=C4=99dala?= <jan@semihalf.com>
Subject: Re: [PATCH v2 0/6] ena: update PMD to cooperate with
 latest ENA firmware
Date: Wed, 29 Jun 2016 13:31:12 +0200
Message-ID: <CANw_3Zdwxe8DmvBK1hi-LS3GXTOWUGr=DO78TrOrVy5JaeGkVw@mail.gmail.com>
References: <1466099690-28085-1-git-send-email-jan@semihalf.com>
 <1466510763-19569-1-git-send-email-jan@semihalf.com>
 <20160624115239.GI13456@bricha3-MOBL3>
 <20160629110139.GC3624@bricha3-MOBL3>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Cc: dev@dpdk.org, ferruh.yigit@intel.com,
 Alexander Matushevsky <alex@annapurnalabs.com>
To: Bruce Richardson <bruce.richardson@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-vk0-f41.google.com (mail-vk0-f41.google.com
 [209.85.213.41]) by dpdk.org (Postfix) with ESMTP id B20D02BB9
 for <dev@dpdk.org>; Wed, 29 Jun 2016 13:31:13 +0200 (CEST)
Received: by mail-vk0-f41.google.com with SMTP id c2so61695210vkg.1
 for <dev@dpdk.org>; Wed, 29 Jun 2016 04:31:13 -0700 (PDT)
In-Reply-To: <20160629110139.GC3624@bricha3-MOBL3>
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>

Bruce,

We've got a small minor fixes and we will create V3 version later this week
(targeting Friday).
What's final deadline for 16.07 integration?

Regards,

  Jan

2016-06-29 13:01 GMT+02:00 Bruce Richardson <bruce.richardson@intel.com>:

> On Fri, Jun 24, 2016 at 12:52:39PM +0100, Bruce Richardson wrote:
> > On Tue, Jun 21, 2016 at 02:05:57PM +0200, Jan Medala wrote:
> > > As requested, big patch splitted into logical pieces for easier review.
> > > Improved style and fixed icc compiler issues.
> > >
> >
> > Thanks for the patch split. However, many of the patches don't have a
> commit
> > message describing (at a high level), what the goal of that patch is and
> how
> > it goes about implementing the changes to achieve that goal. Can you add
> a
> > paragraph or two of commit message to each patch on the set to help
> anyone
> > looking at the code understand what is happening in each patch.
> >
> > Regards,
> > /Bruce
> >
>
> Any update on this set? Is a V3 coming for 16.07 timeframe?
>
> /Bruce
>
>