From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas.monjalon@6wind.com>
Subject: Re: [PATCH 1/2] examples/tep_term: fix offload on VXLAN
	failure
Date: Mon, 12 Sep 2016 11:36:01 +0200
Message-ID: <294735333.lTyYAqE8WY@xps13>
References: <1470297529-100773-1-git-send-email-jianfeng.tan@intel.com>
 <20160911120906.GV23158@yliu-dev.sh.intel.com>
 <ED26CBA2FAD1BF48A8719AEF02201E364E5E3A2A@SHSMSX103.ccr.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: dev@dpdk.org
To: "Tan, Jianfeng" <jianfeng.tan@intel.com>,
 Yuanhan Liu <yuanhan.liu@linux.intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mail-wm0-f42.google.com (mail-wm0-f42.google.com [74.125.82.42])
 by dpdk.org (Postfix) with ESMTP id 6810E558F
 for <dev@dpdk.org>; Mon, 12 Sep 2016 11:36:03 +0200 (CEST)
Received: by mail-wm0-f42.google.com with SMTP id c131so47460959wmh.0
 for <dev@dpdk.org>; Mon, 12 Sep 2016 02:36:03 -0700 (PDT)
In-Reply-To: <ED26CBA2FAD1BF48A8719AEF02201E364E5E3A2A@SHSMSX103.ccr.corp.intel.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>

2016-09-12 08:42, Tan, Jianfeng:
> From: Yuanhan Liu [mailto:yuanhan.liu@linux.intel.com]
> > FYI, my testrobot caught some errors when this patch is applied.
> 
> It's because this patch set has dependency on a previous patch set, which seems a difficult scenario to handle. There's no standard to state the dependency, right?

No there is no standard to state the dependency.
We need one. Actually, there are 3 kinds of dependencies:
	- a well know dependency when sending a patch
	- implicit dependency on the HEAD
	(can fail if a conflicting patch is pushed)
	- dependency on a specific tree (next-*)

I suggest using:
	Depends-on: pw <patchwork-id-of-the-patch>|<tree> <hash>
Examples:
	Depends-on: pw 33000
	Depends-on: master 3643b0f
	Depends-on: next-net f33e00

It won't work well when a patch depends on a pending patch series
because the cover letter has no patchwork identifier.
It will be solved with the next version of patchwork (in few months).
In the meantime, we can point to the first patch of the series.

Comments/ideas?