From mboxrd@z Thu Jan  1 00:00:00 1970
From: =?UTF-8?Q?Micha=C5=82_Krawczyk?= <mk@semihalf.com>
Subject: Re: [PATCH v3 01/27] net/ena: change version number to
	1.1.0
Date: Mon, 11 Jun 2018 11:33:56 +0200
Message-ID: <CAJMMOfN=g-LEYeFxikrWBctPWNZhHnTA4Vs0crjzT_zwz56RQw@mail.gmail.com>
References: <20180607094322.14312-1-mk@semihalf.com>
 <00f98a4c-ef56-5b1e-81f7-8dc3d5f9d47e@intel.com>
 <CAJMMOfMMYGjFTZ7e+fuwko7RswvdgjGGwNxyampsXgLBmgBCxg@mail.gmail.com>
 <2dd37765-f47c-1093-953b-e96624bf3197@intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Cc: Marcin Wojtas <mw@semihalf.com>, Guy Tzalik <gtzalik@amazon.com>,
 Evgeny Schemeilin <evgenys@amazon.com>, dev@dpdk.org,
 "Matushevsky, Alexander" <matua@amazon.com>
To: Ferruh Yigit <ferruh.yigit@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-ua0-f196.google.com (mail-ua0-f196.google.com
 [209.85.217.196]) by dpdk.org (Postfix) with ESMTP id 0DF931E90A
 for <dev@dpdk.org>; Mon, 11 Jun 2018 11:33:58 +0200 (CEST)
Received: by mail-ua0-f196.google.com with SMTP id c23-v6so13070940uan.3
 for <dev@dpdk.org>; Mon, 11 Jun 2018 02:33:57 -0700 (PDT)
In-Reply-To: <2dd37765-f47c-1093-953b-e96624bf3197@intel.com>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://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: <https://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

2018-06-11 11:26 GMT+02:00 Ferruh Yigit <ferruh.yigit@intel.com>:
> On 6/11/2018 9:45 AM, Micha=C5=82 Krawczyk wrote:
>> 2018-06-08 21:45 GMT+02:00 Ferruh Yigit <ferruh.yigit@intel.com>:
>>> On 6/7/2018 10:42 AM, Michal Krawczyk wrote:
>>>> The upcoming patches for the ENA PMD are part of 1.1.0 update of the P=
MD
>>>> and the version number is updated accordingly.
>>>
>>> Does it make sense to add a release notes update to announce driver upd=
ate?
>>
>> Is it possible to move the patch at the end of the uploaded patches,
>> so there won't be need to reupload everything?
>
> Yes release notes update can separate patch, to prevent a new version of =
all
> set, if you are asking this.

That would be great, thanks.

> Or is there any existing documentation patch I am missing?

No, there was no documentation patch.

>
>> The new commit message could be:
>>
>>
>> net/ena: change version number to 1.1.0
>>
>> ENA PMD version 1.1.0 introduces:
>> * Update of the ena_com to the newer version
>> * Remove support of legacy LLQ
>> * Watchdog and device reset
>> * LSC interrupt
>> * Rx out of order completion
>> * Linearization of mbufs with too many fragments
>> * Information about maximum number of Tx and Rx descriptors
>> * Validation of requested id on Tx (for Tx OOO completion)
>> * Likely/unlikely statements
>> * Link speed is now set as none
>> * Other minor bug fixes and changes
>>>
>>>>
>>>> Signed-off-by: Michal Krawczyk <mk@semihalf.com>
>>> <...>
>