From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) by dpdk.org (Postfix) with ESMTP id 68B6858C6 for ; Mon, 22 Jan 2018 08:51:49 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 94EA020CE5; Mon, 22 Jan 2018 02:51:48 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Mon, 22 Jan 2018 02:51:48 -0500 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; s=mesmtp; bh=AGPJOQrORQVPOVk9M5zEzrZa2b IiTHBpAdQwSHc7N38=; b=JlwmkxdoaLZT/JUxV/DMTmvaBrex++tf4OWblkYbAE 5LNay4QTKHt24w0eJ/h/of0TSUnto7sej9tlMg8myL/TJXlncWN/FnSj318/ko3g uj/Mu7QDml8KkDTJHF5tgA3EtwMgaUHOkDwgEr4HHxtSdJJUhIJ68n8koEV2h/bj M= 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; s=fm1; bh=AGPJOQ rORQVPOVk9M5zEzrZa2bIiTHBpAdQwSHc7N38=; b=htPCMVxMRanWJC89z5V4xZ 9YlbsCtT8qbvtABGwp1+E+UfeYbpSrUnpXxDvLyFRe5MeOQmfH+5E+YEIwsIRy/e nJHAY3sOjveCsOV1RtAXUZ7H1I1YvHxhiiyokNQGCNT/dQCJRiCsfMOLVBdle+3e qjLX0zcOkGh+GaKXANn5z2lI1+nATzjQ4R4tqlfScpD1fRiZTA0ianYADnDIACnz 9mzzXCJrRubr0rwi9ux6tgnhbHtlMOxVfa+FNxs0pcOgW/XICt/cG4ARP2CLL3ej qsRAThGG8gBRvyQPHilxtWn6YnrrcGo+w0wD18DT7OenB6bhKNZnqA4kHSskbvYA == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 403A67E3D4; Mon, 22 Jan 2018 02:51:48 -0500 (EST) From: Thomas Monjalon To: wang.yong19@zte.com.cn Cc: dev@dpdk.org, hemant.agrawal@nxp.com, beilei.xing@intel.com, wenzhuo.lu@intel.com, john.griffin@intel.com Date: Mon, 22 Jan 2018 08:51:08 +0100 Message-ID: <30968884.3nNXL6y046@xps> In-Reply-To: <201801221053179672021@zte.com.cn> References: <201801221053179672021@zte.com.cn> MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset="UTF-8" Subject: Re: [dpdk-dev] =?utf-8?b?562U5aSNOiBSZTogIFtQQVRDSCB2MiAxLzRdIG5ldC9k?= =?utf-8?q?paa=3A_add_null_point_check_and_fix_mem_leak?= 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: Mon, 22 Jan 2018 07:51:49 -0000 Hi, 22/01/2018 03:53, wang.yong19@zte.com.cn: > Hi, > I've sent this patch again and it is accepted. > The other 3 pathes have no conflict with the latest master version and th= e titles have described the modification of the patches. > So I need not send the patches for v3, right? Please re-send those which are not integrated yet, with more details, and appropriate title. Thanks > ------------------origin------------------ > From =EF=BC=9A ; > to =EF=BC=9Awang.yong19@zte.com.cn; > cc=EF=BC=9A ; ; ; ; ; > date =EF=BC=9A2018-01-18 07:00 > subject =EF=BC=9ARe: [dpdk-dev] [PATCH v2 1/4] net/dpaa: add null point c= heck and fix mem leak > Hi, >=20 > Please could you rebase on master and keep the acked already given? > Please use --in-reply-to to keep v3 in the same thread as v2. >=20 > Titles are the same for every patches. > Are they all fixing a NULL pointer check and a mem leak? > More details in the commit message may help. >=20 > If they are fixes, a tag Fixes: may help for backports. >=20 > Thanks