From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <thomas@monjalon.net> Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 6A6735599 for <dev@dpdk.org>; Mon, 25 Sep 2017 16:24:22 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id E288221314; Mon, 25 Sep 2017 10:24:21 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Mon, 25 Sep 2017 10:24:21 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc:x-sasl-enc; s=mesmtp; bh=cm/eiEMym2hYV4h 0ueGfVr0Aj1zJIfxPjg5oCoaYjRg=; b=XP4ramDci1gD/i/guABae5XN526Wc3d Qao3gbTKrQ0XJFkky6ZV3rEfUrhpjSnvnzG4KI6u68lzLf1HzgSLDEEQWot7+aLi 8eU7QLN9XLrwdhSHOtw+cDQ3zG/qZ0C/W+f/aNQMxGBnw1bNl1ZlqZI7DQ71j23U vSZv9J3W9jq8= 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-sender:x-me-sender:x-sasl-enc:x-sasl-enc; s= fm1; bh=cm/eiEMym2hYV4h0ueGfVr0Aj1zJIfxPjg5oCoaYjRg=; b=LDwiEol9 s18PPR6lSw0GnuWDYDRkHKhqiJs1m2uHnRFY1+XmgPI+7c9aDomzzwZhvMNWHGEu kArLILT8TkWWIGcmjCaYQNQmyKT6efzDNt77ypnb+Idlv1A9ae58WecirkMvbGFa tWAiR4ogQ677NdD7P4sNqD30cKI8APpXQS3AvtXZx+wvoP19TD8+4Sn1Ea+2XyEU huDLqrJi4U2/ziAQiss46zCiKz2TcpC84KnBERjHbXGFUka/6fCv+9Ai6ragrYQW 9Zg0KAbtj4afbWHmiQPpc3xSgJeAdcPPFruoIJGWn3b01enZ8VNwfCiXXTDxdd6v vo28Tkk6y1mNqg== X-ME-Sender: <xms:lRHJWRARXwrnjln-lVRZWsvcHqK5RtXXkEvhlUAsyJb7JAYvNzRpsw> X-Sasl-enc: BD5DBQsD3vY3cjK9Fpq98G2p/NmvesUlv1xlhrGTFoEt 1506349461 Received: from xps.localnet (host.78.145.23.62.rev.coltfrance.com [62.23.145.78]) by mail.messagingengine.com (Postfix) with ESMTPA id 93AED24A9A; Mon, 25 Sep 2017 10:24:21 -0400 (EDT) From: Thomas Monjalon <thomas@monjalon.net> To: Ferruh Yigit <ferruh.yigit@intel.com> Cc: Bruce Richardson <bruce.richardson@intel.com>, Andrew Rybchenko <arybchenko@solarflare.com>, dev@dpdk.org, Chas Williams <chas3@att.com> Date: Mon, 25 Sep 2017 16:24:21 +0200 Message-ID: <1809804.5fyl0q0CTl@xps> In-Reply-To: <e987c543-fb5c-6143-87b2-f9d7c205ba59@intel.com> References: <1506322206-30233-1-git-send-email-arybchenko@solarflare.com> <510427f2-5761-024f-791a-7d44c58231c9@intel.com> <e987c543-fb5c-6143-87b2-f9d7c205ba59@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH] net/af_packet: fix build failure because of unused parameter X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions <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> X-List-Received-Date: Mon, 25 Sep 2017 14:24:22 -0000 25/09/2017 12:06, Ferruh Yigit: > On 9/25/2017 10:53 AM, Ferruh Yigit wrote: > > On 9/25/2017 10:40 AM, Bruce Richardson wrote: > >> On Mon, Sep 25, 2017 at 09:42:56AM +0100, Ferruh Yigit wrote: > >>> It is a little to late for this, I already sent a pull-request with this > >>> patch. So fix will need to be a separate patch. > >>> > >> Pull request hasn't actually been pulled yet, so you should be able to > >> supercede it by a later one, right? > > > > Technically yes, and easy to do, but it will be confusing. I was taking > > pull-request as code freeze in sub-tree. > > > > If there are multiple pull-request for a tree, how can one be sure which > > ones has been pulled and what to expect in main repo, and verify what > > has been merged? > > > > As above said, if Thomas thinks this is OK, I can send another pull request? > > What about Thomas doing the squash while applying to the main repo, so > that main repo won't be broken and there won't be multiple pull requests > around? Yes, no need of sending a new pull request.