From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id 9621A2BE3 for ; Fri, 26 Oct 2018 19:43:48 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 2260521C5F; Fri, 26 Oct 2018 13:43:48 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 26 Oct 2018 13:43:48 -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=tH+cA+QanpjB9rF3Li+7EGe0OmPzaiF9xNxmwhd/oG8=; b=DnqjvrLf3ZUe 3vZVqt+lqZGw3+Gw1JUzjw9TVyebtNZ5fWezt5qIaAFBNSkub1IptdF96TgH1LLd 2+mejDILkUIDODIhn+j4YEldxFpwNqUm8ck1F4OnnSzP/CplyuQLdJMB032w3F1l T8hv2mn+7bnAbQaAKjV4T9Z55sdzvZ0= 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=fm1; bh=tH+cA+QanpjB9rF3Li+7EGe0OmPzaiF9xNxmwhd/o G8=; b=x+vMsKit4FbgBWGrOQaWlZ9BRpK3xyxRUeSbUaFxqMkPlca5QBJTXhbQd QbtDVLcmBU8U69afTX2BrRvoAjhff2H01fpGT/HYy0/+3vqARs9iLFy/299rCyJw GcNo3QKKyJqDs1czPuWqXESepuBhsDmORWFUJDucRsLCc+Fz7dxTFgxTDqIiAQzG 7Et411yqqD6NX8IDnL+OtbkVQal31bUKd1FpLoPcO/1ARXa3akNr1W2L/Gm8S1I8 neR8ss1j8Uc0TdebIMT5y2rqJGzscZ8eyOiK4n5koeboZ7cN9d7SUX4P4jU72sNW 7auvoBsWieFBpl1fot5Oxbz8ZTdGw== X-ME-Sender: X-ME-Proxy: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 9E588E491F; Fri, 26 Oct 2018 13:43:45 -0400 (EDT) From: Thomas Monjalon To: Dan Gora Cc: dev@dpdk.org, Ferruh Yigit , Igor Ryzhov , Stephen Hemminger , bruce.richardson@intel.com, nhorman@tuxdriver.com Date: Fri, 26 Oct 2018 19:43:50 +0200 Message-ID: <1811735.4e0LzYgYzU@xps> In-Reply-To: <816862ee-8042-4c66-93c8-6ceb57be4999@intel.com> References: <20180911232906.18352-1-dg@adax.com> <20181024222631.30461-1-dg@adax.com> <816862ee-8042-4c66-93c8-6ceb57be4999@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v7 0/5] kni: add API to set link status on kernel interface 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: Fri, 26 Oct 2018 17:43:48 -0000 25/10/2018 14:30, Ferruh Yigit: > On 10/24/2018 11:26 PM, Dan Gora wrote: > >> Note that checkpatches.sh compains about patch 1/5, but this appears > >> to be a bug with check-symbol-change or something. If I move the > >> fragment of the patch modifying rte_kni_version.map to the bottom of > >> the patch file, it doesn't complain any more... I just don't really > >> have time to investigate this right now. Yes we have some false positives with this tool. Neil, please, would you have time to look at it? > > Dan Gora (5): > > kni: add API to set link status on kernel interface > > kni: set default carrier state of interface > > examples/kni: monitor and update link status continually > > examples/kni: add log msgs to show and clear stats > > examples/kni: improve zeroing statistics > > For series, > Acked-by: Ferruh Yigit Applied with a fix for meson build