From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id 0006A1B4C9 for ; Thu, 22 Nov 2018 18:46:25 +0100 (CET) Received: from smtp.corp.redhat.com (int-mx03.intmail.prod.int.phx2.redhat.com [10.5.11.13]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id 239FE307D840; Thu, 22 Nov 2018 17:46:25 +0000 (UTC) Received: from ktraynor.remote.csb (unknown [10.36.118.7]) by smtp.corp.redhat.com (Postfix) with ESMTP id 5D3FA6061D; Thu, 22 Nov 2018 17:46:19 +0000 (UTC) From: Kevin Traynor To: dpdk stable Cc: Bruce Richardson , Gavin Hu , Honnappa Nagarahalli , Ilya Maximets , Maxime Coquelin , Viacheslav Ovsiienko , Yipeng Wang Date: Thu, 22 Nov 2018 17:46:05 +0000 Message-Id: <20181122174605.14744-1-ktraynor@redhat.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Scanned-By: MIMEDefang 2.79 on 10.5.11.13 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.48]); Thu, 22 Nov 2018 17:46:25 +0000 (UTC) Subject: [dpdk-stable] please help backporting some patches to stable release 18.08.1 X-BeenThere: stable@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches for DPDK stable branches List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Nov 2018 17:46:26 -0000 Hi commit authors (and maintainers), I didn't manage to apply following commits from upstream to stable branch 18.08: conflict happens. I'm wondering can the authors check the following list and backport those patches belong to you? FYI, branch 18.08 is located at tree: git://dpdk.org/dpdk-stable It'd be great if you could do that in one or two weeks. Also, please add a heading line like below before the commit log body: [ backported from upstream commit xxx ] Example: http://dpdk.org/browse/dpdk-stable/commit/?h=16.07&id=c4831394c7d1944d8ec27d52c22997f20d19718e Also please mention the target stable in the subject line, as we have more than one at the same time, for example: [PATCH 18.08] foo/bar: fix baz With git send-email, this can be achieved by appending the parameter: --subject-prefix='18.08' Please let me know if you have any comments, say, need more time, or it's worthless to packport it. And please send it to "stable@dpdk.org", but not "dev@dpdk.org". Thanks. Kevin Traynor --- 40f8e9c28 Honnappa Nagarahalli hash: separate multi-writer from r/w concurrency 57b4d90b5 Maxime Coquelin vhost: fix payload size of reply c4301b9ca Viacheslav Ovsiienko net/mlx5: fix flow counters creation 57660eba7 Yipeng Wang test/hash: add r/w concurrency to autotest