From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com [148.163.156.1]) by dpdk.org (Postfix) with ESMTP id B5E422BD5 for ; Thu, 9 May 2019 00:50:50 +0200 (CEST) Received: from pps.filterd (m0098399.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x48MfwSb131773 for ; Wed, 8 May 2019 18:50:49 -0400 Received: from e36.co.us.ibm.com (e36.co.us.ibm.com [32.97.110.154]) by mx0a-001b2d01.pphosted.com with ESMTP id 2sc60d5qj5-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Wed, 08 May 2019 18:50:49 -0400 Received: from localhost by e36.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 8 May 2019 23:50:49 +0100 Received: from b03cxnp08026.gho.boulder.ibm.com (9.17.130.18) by e36.co.us.ibm.com (192.168.1.136) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Wed, 8 May 2019 23:50:46 +0100 Received: from b03ledav003.gho.boulder.ibm.com (b03ledav003.gho.boulder.ibm.com [9.17.130.234]) by b03cxnp08026.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id x48Mojd711403682 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 8 May 2019 22:50:45 GMT Received: from b03ledav003.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 5A46B6A04F; Wed, 8 May 2019 22:50:45 +0000 (GMT) Received: from b03ledav003.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 2A83F6A051; Wed, 8 May 2019 22:50:45 +0000 (GMT) Received: from davids-mbp.usor.ibm.com (unknown [9.70.84.57]) by b03ledav003.gho.boulder.ibm.com (Postfix) with ESMTP; Wed, 8 May 2019 22:50:44 +0000 (GMT) To: Thomas Monjalon Cc: dev@dpdk.org References: <1557349328-25783-1-git-send-email-drc@linux.vnet.ibm.com> <2307873.h1T1EuVh32@xps> From: David Christensen Date: Wed, 8 May 2019 15:50:44 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <2307873.h1T1EuVh32@xps> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TM-AS-GCONF: 00 x-cbid: 19050822-0020-0000-0000-00000EE58723 X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00011073; HX=3.00000242; KW=3.00000007; PH=3.00000004; SC=3.00000285; SDB=6.01200550; UDB=6.00629932; IPR=6.00981437; MB=3.00026799; MTD=3.00000008; XFM=3.00000015; UTC=2019-05-08 22:50:47 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 19050822-0021-0000-0000-000065BF9456 Message-Id: <17079a97-4966-fdb9-1c89-7017bc33f3a3@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-05-08_12:, , signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1905080135 Subject: Re: [dpdk-dev] [PATCH v3 1/4] test: fix typo in print statement X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 08 May 2019 22:50:51 -0000 > It seems your emails are not threaded at all. > It makes really hard to review them. > All patches of a patchset must be in the same thread, > ideally with a cover letter. > All versions of a patchset must be in the same thread, > ideally with the cover letter v1 being the common ancestor. > Please check http://core.dpdk.org/contribute/#send > > You need also to report the acks you got in previous versions. I messed up with the first post in the patch series (no 0/4 message). In order to fix the long line problem, which post would you suggest I use as an anchor for my reply-to? The original v1 1/4, the v3 1/4, or some other? Dave From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 0E643A0096 for ; Thu, 9 May 2019 00:50:52 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id BF62934F0; Thu, 9 May 2019 00:50:51 +0200 (CEST) Received: from mx0a-001b2d01.pphosted.com (mx0a-001b2d01.pphosted.com [148.163.156.1]) by dpdk.org (Postfix) with ESMTP id B5E422BD5 for ; Thu, 9 May 2019 00:50:50 +0200 (CEST) Received: from pps.filterd (m0098399.ppops.net [127.0.0.1]) by mx0a-001b2d01.pphosted.com (8.16.0.27/8.16.0.27) with SMTP id x48MfwSb131773 for ; Wed, 8 May 2019 18:50:49 -0400 Received: from e36.co.us.ibm.com (e36.co.us.ibm.com [32.97.110.154]) by mx0a-001b2d01.pphosted.com with ESMTP id 2sc60d5qj5-1 (version=TLSv1.2 cipher=AES256-GCM-SHA384 bits=256 verify=NOT) for ; Wed, 08 May 2019 18:50:49 -0400 Received: from localhost by e36.co.us.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Wed, 8 May 2019 23:50:49 +0100 Received: from b03cxnp08026.gho.boulder.ibm.com (9.17.130.18) by e36.co.us.ibm.com (192.168.1.136) with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted; (version=TLSv1/SSLv3 cipher=AES256-GCM-SHA384 bits=256/256) Wed, 8 May 2019 23:50:46 +0100 Received: from b03ledav003.gho.boulder.ibm.com (b03ledav003.gho.boulder.ibm.com [9.17.130.234]) by b03cxnp08026.gho.boulder.ibm.com (8.14.9/8.14.9/NCO v10.0) with ESMTP id x48Mojd711403682 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 8 May 2019 22:50:45 GMT Received: from b03ledav003.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 5A46B6A04F; Wed, 8 May 2019 22:50:45 +0000 (GMT) Received: from b03ledav003.gho.boulder.ibm.com (unknown [127.0.0.1]) by IMSVA (Postfix) with ESMTP id 2A83F6A051; Wed, 8 May 2019 22:50:45 +0000 (GMT) Received: from davids-mbp.usor.ibm.com (unknown [9.70.84.57]) by b03ledav003.gho.boulder.ibm.com (Postfix) with ESMTP; Wed, 8 May 2019 22:50:44 +0000 (GMT) To: Thomas Monjalon Cc: dev@dpdk.org References: <1557349328-25783-1-git-send-email-drc@linux.vnet.ibm.com> <2307873.h1T1EuVh32@xps> From: David Christensen Date: Wed, 8 May 2019 15:50:44 -0700 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <2307873.h1T1EuVh32@xps> Content-Type: text/plain; charset="UTF-8"; format="flowed" Content-Language: en-US Content-Transfer-Encoding: 7bit X-TM-AS-GCONF: 00 x-cbid: 19050822-0020-0000-0000-00000EE58723 X-IBM-SpamModules-Scores: X-IBM-SpamModules-Versions: BY=3.00011073; HX=3.00000242; KW=3.00000007; PH=3.00000004; SC=3.00000285; SDB=6.01200550; UDB=6.00629932; IPR=6.00981437; MB=3.00026799; MTD=3.00000008; XFM=3.00000015; UTC=2019-05-08 22:50:47 X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused x-cbparentid: 19050822-0021-0000-0000-000065BF9456 Message-Id: <17079a97-4966-fdb9-1c89-7017bc33f3a3@linux.vnet.ibm.com> X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-05-08_12:, , signatures=0 X-Proofpoint-Spam-Details: rule=outbound_notspam policy=outbound score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1905080135 Subject: Re: [dpdk-dev] [PATCH v3 1/4] test: fix typo in print statement X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Message-ID: <20190508225044.LHyP2PiC3FpUgV9PwHX2ouNpwPMgXy7oO73lU67Sm5g@z> > It seems your emails are not threaded at all. > It makes really hard to review them. > All patches of a patchset must be in the same thread, > ideally with a cover letter. > All versions of a patchset must be in the same thread, > ideally with the cover letter v1 being the common ancestor. > Please check http://core.dpdk.org/contribute/#send > > You need also to report the acks you got in previous versions. I messed up with the first post in the patch series (no 0/4 message). In order to fix the long line problem, which post would you suggest I use as an anchor for my reply-to? The original v1 1/4, the v3 1/4, or some other? Dave