From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH 00/15] net/enic: 19.05 updates
Date: Fri, 01 Mar 2019 15:26:24 +0100
Message-ID: <16525514.hJAoYjsEvP@xps>
References: <20190228070317.17002-1-hyonkim@cisco.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@intel.com>,
 John Daley <johndale@cisco.com>
To: Hyong Youb Kim <hyonkim@cisco.com>
Return-path: <dev-bounces@dpdk.org>
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com
 [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id E5EEB3256
 for <dev@dpdk.org>; Fri,  1 Mar 2019 15:26:27 +0100 (CET)
In-Reply-To: <20190228070317.17002-1-hyonkim@cisco.com>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://mails.dpdk.org/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://mails.dpdk.org/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://mails.dpdk.org/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

Hi,

> Hyong Youb Kim (15):
>   net/enic: remove unused code
>   net/enic: fix flow director SCTP matching
>   net/enic: fix SCTP match for flow API
>   net/enic: allow flow mark ID 0
>   net/enic: check for unsupported flow item types
>   net/enic: enable limited RSS flow action
>   net/enic: enable limited PASSTHRU flow action
>   net/enic: move arguments into struct
>   net/enic: enable limited support for RAW flow item
>   net/enic: initialize VXLAN port regardless of overlay offload
>   net/enic: fix a couple issues with VXLAN match
>   net/enic: fix an endian bug in VLAN match
>   net/enic: fix several issues with inner packet matching
>   doc: update enic guide
>   doc: update release notes for enic

It is better to update the doc in the patch of the code change.
It would allow to find the code changes by looking at the doc history
(with "git blame" or others).
The other benefit is to avoid some "noise" in the git history for doc.

Thanks