From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id AF16ADE0 for ; Fri, 22 Jan 2016 22:31:41 +0100 (CET) Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga101.jf.intel.com with ESMTP; 22 Jan 2016 13:31:40 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,333,1449561600"; d="scan'208";a="34443156" Received: from bricha3-mobl3.ger.corp.intel.com ([10.24.26.66]) by fmsmga004.fm.intel.com with SMTP; 22 Jan 2016 13:31:39 -0800 Received: by (sSMTP sendmail emulation); Fri, 22 Jan 2016 13:31:38 -0700 Date: Fri, 22 Jan 2016 13:31:38 -0800 From: Bruce Richardson To: Wang Xiao W Message-ID: <20160122213137.GA19964@bricha3-MOBL3> References: <1453372561-11431-1-git-send-email-xiao.w.wang@intel.com> <1453372561-11431-16-git-send-email-xiao.w.wang@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1453372561-11431-16-git-send-email-xiao.w.wang@intel.com> Organization: Intel Shannon Ltd. User-Agent: Mutt/1.5.23 (2014-03-12) Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH 15/16] fm10k: use default mailbox message handler for pf X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jan 2016 21:31:42 -0000 On Thu, Jan 21, 2016 at 06:36:00PM +0800, Wang Xiao W wrote: > The new share code makes fm10k_msg_update_pvid_pf function static, so we can > not refer to it now in fm10k_ethdev.c. The registered pf handler is almost the > same as the default pf handler, removing it has no impact on mailbox. > > Signed-off-by: Wang Xiao W What patch makes the function static, as we need to ensure that the build is not broken by having this patch in the wrong place in the patchset? Also, it seems strange having this patch in the middle of a series of base code updates - perhaps it should go first, so that all base code update patches can go one after the other. /Bruce > --- > drivers/net/fm10k/fm10k_ethdev.c | 17 ++--------------- > 1 file changed, 2 insertions(+), 15 deletions(-) > > diff --git a/drivers/net/fm10k/fm10k_ethdev.c b/drivers/net/fm10k/fm10k_ethdev.c > index e967628..a118cf4 100644 > --- a/drivers/net/fm10k/fm10k_ethdev.c > +++ b/drivers/net/fm10k/fm10k_ethdev.c > @@ -2367,29 +2367,16 @@ static const struct fm10k_msg_data fm10k_msgdata_vf[] = { > FM10K_TLV_MSG_ERROR_HANDLER(fm10k_tlv_msg_error), > }; > > -/* Mailbox message handler in PF */ > -static const struct fm10k_msg_data fm10k_msgdata_pf[] = { > - FM10K_PF_MSG_ERR_HANDLER(XCAST_MODES, fm10k_msg_err_pf), > - FM10K_PF_MSG_ERR_HANDLER(UPDATE_MAC_FWD_RULE, fm10k_msg_err_pf), > - FM10K_PF_MSG_LPORT_MAP_HANDLER(fm10k_msg_lport_map_pf), > - FM10K_PF_MSG_ERR_HANDLER(LPORT_CREATE, fm10k_msg_err_pf), > - FM10K_PF_MSG_ERR_HANDLER(LPORT_DELETE, fm10k_msg_err_pf), > - FM10K_PF_MSG_UPDATE_PVID_HANDLER(fm10k_msg_update_pvid_pf), > - FM10K_TLV_MSG_ERROR_HANDLER(fm10k_tlv_msg_error), > -}; > - > static int > fm10k_setup_mbx_service(struct fm10k_hw *hw) > { > - int err; > + int err = 0; > > /* Initialize mailbox lock */ > fm10k_mbx_initlock(hw); > > /* Replace default message handler with new ones */ > - if (hw->mac.type == fm10k_mac_pf) > - err = hw->mbx.ops.register_handlers(&hw->mbx, fm10k_msgdata_pf); > - else > + if (hw->mac.type == fm10k_mac_vf) > err = hw->mbx.ops.register_handlers(&hw->mbx, fm10k_msgdata_vf); > > if (err) { > -- > 1.9.3 >