DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Tan, Jianfeng" <jianfeng.tan@intel.com>,
	Yuanhan Liu <yuanhan.liu@linux.intel.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 1/2] examples/tep_term: fix offload on VXLAN failure
Date: Mon, 12 Sep 2016 11:36:01 +0200	[thread overview]
Message-ID: <294735333.lTyYAqE8WY@xps13> (raw)
In-Reply-To: <ED26CBA2FAD1BF48A8719AEF02201E364E5E3A2A@SHSMSX103.ccr.corp.intel.com>

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?

  reply	other threads:[~2016-09-12  9:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-04  7:58 [dpdk-dev] [PATCH 0/2] Two offloading issues of tep_term Jianfeng Tan
2016-08-04  7:58 ` [dpdk-dev] [PATCH 1/2] examples/tep_term: fix offload on VXLAN failure Jianfeng Tan
2016-09-11 12:09   ` Yuanhan Liu
2016-09-12  8:42     ` Tan, Jianfeng
2016-09-12  9:36       ` Thomas Monjalon [this message]
2016-09-13  0:50         ` Tan, Jianfeng
2016-09-13  2:40         ` Yuanhan Liu
2016-08-04  7:58 ` [dpdk-dev] [PATCH 2/2] examples/tep_term: fix inner L4 checksum failure Jianfeng Tan
2016-10-13  9:39 ` [dpdk-dev] [PATCH 0/2] Two offloading issues of tep_term Thomas Monjalon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=294735333.lTyYAqE8WY@xps13 \
    --to=thomas.monjalon@6wind.com \
    --cc=dev@dpdk.org \
    --cc=jianfeng.tan@intel.com \
    --cc=yuanhan.liu@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).