From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: =?utf-8?b?562U5aSNOiBSZTogIFtQQVRDSCB2MiAxLzRdIG5ldC9k?= =?utf-8?q?paa=3A_add_null_point_check_and_fix_mem_leak?= Date: Mon, 22 Jan 2018 08:51:08 +0100 Message-ID: <30968884.3nNXL6y046@xps> References: <201801221053179672021@zte.com.cn> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Cc: dev@dpdk.org, hemant.agrawal@nxp.com, beilei.xing@intel.com, wenzhuo.lu@intel.com, john.griffin@intel.com To: wang.yong19@zte.com.cn 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) In-Reply-To: <201801221053179672021@zte.com.cn> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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