From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id 2471EA00B8; Mon, 28 Oct 2019 06:51:28 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id EA9C31BEF9; Mon, 28 Oct 2019 06:51:27 +0100 (CET) Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id BA9551BEBD for ; Mon, 28 Oct 2019 06:51:26 +0100 (CET) X-Amp-Result: UNKNOWN X-Amp-Original-Verdict: FILE UNKNOWN X-Amp-File-Uploaded: False Received: from orsmga003.jf.intel.com ([10.7.209.27]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 27 Oct 2019 22:51:25 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.68,239,1569308400"; d="scan'208";a="202421241" Received: from yexl-server.sh.intel.com (HELO localhost) ([10.67.117.17]) by orsmga003.jf.intel.com with ESMTP; 27 Oct 2019 22:51:24 -0700 Date: Mon, 28 Oct 2019 13:47:58 +0800 From: Ye Xiaolong To: Thomas Monjalon Cc: David Marchand , Ferruh Yigit , Tianfei zhang , dev Message-ID: <20191028054758.GC33024@intel.com> References: <20190917222459.19097-1-tianfei.zhang@intel.com> <71ae89af-e271-cb72-dd8f-e6d08aeee6d4@intel.com> <1908591.FNZmaogfpl@xps> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1908591.FNZmaogfpl@xps> User-Agent: Mutt/1.9.4 (2018-02-28) Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] raw/ifpga/base: dereference before null check 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: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 10/25, Thomas Monjalon wrote: >25/10/2019 13:47, David Marchand: >> On Fri, Oct 25, 2019 at 12:30 PM Ferruh Yigit wrote: >> > > Reviewed-by: Xiaolong Ye >> > > >> > > Applied to dpdk-next-net-intel. Thanks. >> > > >> > >> > Should we update the MAINTAINERS file to say that "drivers/raw/ifpga" merges to >> > the next-net-intel? >> >> Thanks, this area is, a bit, gray to me. >> So a clarification is welcome. > >Yes I think it is OK to get raw/ifpga in next-net-intel. > > Done, just send a patch for it. Thanks, Xiaolong