From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [dpdk-stable] [PATCH v3] crypto/scheduler: add mode
	specific option support
Date: Wed, 05 Apr 2017 13:43:24 +0200
Message-ID: <2931110.MkCoQrrDzj@xps13>
References: <1490974226-40957-1-git-send-email-roy.fan.zhang@intel.com>
 <1491382943-106849-1-git-send-email-roy.fan.zhang@intel.com>
 <fed5cc55-5720-7b5e-27ca-91b80ee8711b@intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: stable@dpdk.org, Fan Zhang <roy.fan.zhang@intel.com>, dev@dpdk.org,
 pablo.de.lara.guarch@intel.com
To: Declan Doherty <declan.doherty@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-wr0-f182.google.com (mail-wr0-f182.google.com
 [209.85.128.182]) by dpdk.org (Postfix) with ESMTP id A32CF2C6E
 for <dev@dpdk.org>; Wed,  5 Apr 2017 13:43:27 +0200 (CEST)
Received: by mail-wr0-f182.google.com with SMTP id w11so9916677wrc.3
 for <dev@dpdk.org>; Wed, 05 Apr 2017 04:43:27 -0700 (PDT)
In-Reply-To: <fed5cc55-5720-7b5e-27ca-91b80ee8711b@intel.com>
List-Id: DPDK patches and discussions <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>

2017-04-05 11:02, Declan Doherty:
> On 05/04/2017 10:02 AM, Fan Zhang wrote:
> > Some scheduling modes may need extra options to be configured,
> > this patch adds the function prototype for setting/getting
> > options.
> >
> > Signed-off-by: Fan Zhang <roy.fan.zhang@intel.com>
> > ---
> ...
> >
> 
> Fan, could you send a documentation patch with a update to the scheduler 
> documentation about the new option introduced in this patch.
> 
> Acked-by: Declan Doherty <declan.doherty@intel.com>

It is always better to have this kind of documentation update
within the same patch as code update.