From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <thomas@monjalon.net> Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id D349A2B87 for <dev@dpdk.org>; Thu, 9 May 2019 22:03:19 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 4FE7723DB5; Thu, 9 May 2019 16:03:19 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 09 May 2019 16:03:19 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=9plPjllNggvnzk8WfHxHCVwodce94CH1YK80CqRBERc=; b=c4dwLrZI+XsX h1Jt8TKAwLYkalEpb8+2GNNw4TOBT5x4XX2eZiQCFjGjFBjO4p9JNq3XS/K1/l7u cn7WjfBrkCcp0nIUN6jQmyO9F9YYeTSU1dDB95qf3wMdRfyd0osjYNslPR1JKSBu eksLDMigR5+cRnPbkFUPsWAMCWLI1qQ= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=9plPjllNggvnzk8WfHxHCVwodce94CH1YK80CqRBE Rc=; b=2A8+hxHGCJBnRZnrEUZOKD+j6mDZY158DkmkYlaq9opP/F2CCF9zE/Dad 9ZSlg4ex4RZ645d0s5ZvTPD8al1BLIzj9EApEoNC+2BrJADacD7iRXpIkXOF4kaU YPP/VYWOKSm+3CWLN8KYgq/R0mqz2NqY1qX8f5B8Wn9PI6RVsG+yM6En1/+qEtfe KOmR/RZeH9+R9LKfDwMJElbPUGbk69gMP9WrVmFKV6Fm9TlE+dbVthEgH+0zwkSN TJkJ3bcVfamARhl8Ve2qKoOPTDjiDuair18Yod22YUnNLo1TviHYoDlyB40w2o9T kCioL+J7juEIjbkOi52hk8yQFQd/Q== X-ME-Sender: <xms:hofUXIZsSKRe4WB0O50GZ9fkFcG-OCXE8JOtoeFfcudgNI_D-XFHnA> X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrkeeigdekhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhephffvufffkfgjfhgggfgtsehtufertd dttddvnecuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceothhhohhmrghssehm ohhnjhgrlhhonhdrnhgvtheqnecuffhomhgrihhnpeguphgukhdrohhrghenucfkphepje ejrddufeegrddvtdefrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgr shesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: <xmx:hofUXLIcqSweYkokO9EtNHbhrmDz8ZhAhSf7l4WW5wuxgK9Fb6Cfpg> <xmx:hofUXGCfQi7Z0OoUzA379oJwy33Xye5xkP0s8ycD5RKai5oDWNAJWw> <xmx:hofUXAqdn8TghzCu3CLMECYzR79vR2elL0ce6sOC4UNzwr1STJ5hoA> <xmx:h4fUXKkIdCH-zpChsGGpmEtIxc3fyN2GgHWcgwJxRPnjeAWyEYebMg> Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 1E4D88005A; Thu, 9 May 2019 16:03:18 -0400 (EDT) From: Thomas Monjalon <thomas@monjalon.net> To: David Christensen <drc@linux.vnet.ibm.com> Cc: dev@dpdk.org Date: Thu, 09 May 2019 22:03:16 +0200 Message-ID: <2355853.FVELj8bnlP@xps> In-Reply-To: <3114423.JV8VNAVq30@xps> References: <1557349328-25783-1-git-send-email-drc@linux.vnet.ibm.com> <17079a97-4966-fdb9-1c89-7017bc33f3a3@linux.vnet.ibm.com> <3114423.JV8VNAVq30@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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 <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Thu, 09 May 2019 20:03:20 -0000 09/05/2019 09:46, Thomas Monjalon: > 09/05/2019 00:50, David Christensen: > > > 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? > > The patches of v3 are not threaded together, > so when doing a v4 you can skip --in-reply-to. Series applied with added acks, fixes lines, etc, thanks. From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <dev-bounces@dpdk.org> Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id 3ED6DA0096 for <public@inbox.dpdk.org>; Thu, 9 May 2019 22:03:22 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id A411F44C3; Thu, 9 May 2019 22:03:20 +0200 (CEST) Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) by dpdk.org (Postfix) with ESMTP id D349A2B87 for <dev@dpdk.org>; Thu, 9 May 2019 22:03:19 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 4FE7723DB5; Thu, 9 May 2019 16:03:19 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Thu, 09 May 2019 16:03:19 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= from:to:cc:subject:date:message-id:in-reply-to:references :mime-version:content-transfer-encoding:content-type; s=mesmtp; bh=9plPjllNggvnzk8WfHxHCVwodce94CH1YK80CqRBERc=; b=c4dwLrZI+XsX h1Jt8TKAwLYkalEpb8+2GNNw4TOBT5x4XX2eZiQCFjGjFBjO4p9JNq3XS/K1/l7u cn7WjfBrkCcp0nIUN6jQmyO9F9YYeTSU1dDB95qf3wMdRfyd0osjYNslPR1JKSBu eksLDMigR5+cRnPbkFUPsWAMCWLI1qQ= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm2; bh=9plPjllNggvnzk8WfHxHCVwodce94CH1YK80CqRBE Rc=; b=2A8+hxHGCJBnRZnrEUZOKD+j6mDZY158DkmkYlaq9opP/F2CCF9zE/Dad 9ZSlg4ex4RZ645d0s5ZvTPD8al1BLIzj9EApEoNC+2BrJADacD7iRXpIkXOF4kaU YPP/VYWOKSm+3CWLN8KYgq/R0mqz2NqY1qX8f5B8Wn9PI6RVsG+yM6En1/+qEtfe KOmR/RZeH9+R9LKfDwMJElbPUGbk69gMP9WrVmFKV6Fm9TlE+dbVthEgH+0zwkSN TJkJ3bcVfamARhl8Ve2qKoOPTDjiDuair18Yod22YUnNLo1TviHYoDlyB40w2o9T kCioL+J7juEIjbkOi52hk8yQFQd/Q== X-ME-Sender: <xms:hofUXIZsSKRe4WB0O50GZ9fkFcG-OCXE8JOtoeFfcudgNI_D-XFHnA> X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduuddrkeeigdekhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhephffvufffkfgjfhgggfgtsehtufertd dttddvnecuhfhrohhmpefvhhhomhgrshcuofhonhhjrghlohhnuceothhhohhmrghssehm ohhnjhgrlhhonhdrnhgvtheqnecuffhomhgrihhnpeguphgukhdrohhrghenucfkphepje ejrddufeegrddvtdefrddukeegnecurfgrrhgrmhepmhgrihhlfhhrohhmpehthhhomhgr shesmhhonhhjrghlohhnrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd X-ME-Proxy: <xmx:hofUXLIcqSweYkokO9EtNHbhrmDz8ZhAhSf7l4WW5wuxgK9Fb6Cfpg> <xmx:hofUXGCfQi7Z0OoUzA379oJwy33Xye5xkP0s8ycD5RKai5oDWNAJWw> <xmx:hofUXAqdn8TghzCu3CLMECYzR79vR2elL0ce6sOC4UNzwr1STJ5hoA> <xmx:h4fUXKkIdCH-zpChsGGpmEtIxc3fyN2GgHWcgwJxRPnjeAWyEYebMg> Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 1E4D88005A; Thu, 9 May 2019 16:03:18 -0400 (EDT) From: Thomas Monjalon <thomas@monjalon.net> To: David Christensen <drc@linux.vnet.ibm.com> Cc: dev@dpdk.org Date: Thu, 09 May 2019 22:03:16 +0200 Message-ID: <2355853.FVELj8bnlP@xps> In-Reply-To: <3114423.JV8VNAVq30@xps> References: <1557349328-25783-1-git-send-email-drc@linux.vnet.ibm.com> <17079a97-4966-fdb9-1c89-7017bc33f3a3@linux.vnet.ibm.com> <3114423.JV8VNAVq30@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="UTF-8" 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 <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org Sender: "dev" <dev-bounces@dpdk.org> Message-ID: <20190509200316.-dH3KY0Hhxxdzr8sRQ4lw-sL8jwO38_Y-A1rkrc6Lms@z> 09/05/2019 09:46, Thomas Monjalon: > 09/05/2019 00:50, David Christensen: > > > 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? > > The patches of v3 are not threaded together, > so when doing a v4 you can skip --in-reply-to. Series applied with added acks, fixes lines, etc, thanks.