Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752607AbdF3TZQ (ORCPT ); Fri, 30 Jun 2017 15:25:16 -0400 Received: from mail-oi0-f68.google.com ([209.85.218.68]:33015 "EHLO mail-oi0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752399AbdF3TZO (ORCPT ); Fri, 30 Jun 2017 15:25:14 -0400 MIME-Version: 1.0 In-Reply-To: References: <20170630154412.3575760-1-arnd@arndb.de> From: Arnd Bergmann Date: Fri, 30 Jun 2017 21:25:13 +0200 X-Google-Sender-Auth: jicpGdyG5V5dHeIXZG-Xwqz5GWg Message-ID: Subject: Re: [PATCH] [net-next] net/mlx5: include wq.o in non-ethernet build for FPGA To: Ilan Tayari Cc: Saeed Mahameed , Matan Barak , Leon Romanovsky , "David S. Miller" , Boris Pismenny , Or Gerlitz , Hadar Hen Zion , Kamal Heib , Maor Gottlieb , Mohamad Haj Yahia , Aviv Heller , "netdev@vger.kernel.org" , "linux-rdma@vger.kernel.org" , "linux-kernel@vger.kernel.org" Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1141 Lines: 29 On Fri, Jun 30, 2017 at 8:58 PM, Ilan Tayari wrote: >> diff --git a/drivers/net/ethernet/mellanox/mlx5/core/Makefile >> b/drivers/net/ethernet/mellanox/mlx5/core/Makefile >> index ca367445f864..50fe9e3c5dc2 100644 >> --- a/drivers/net/ethernet/mellanox/mlx5/core/Makefile >> +++ b/drivers/net/ethernet/mellanox/mlx5/core/Makefile >> @@ -9,7 +9,7 @@ mlx5_core-y := main.o cmd.o debugfs.o fw.o eq.o uar.o >> pagealloc.o \ >> mlx5_core-$(CONFIG_MLX5_ACCEL) += accel/ipsec.o >> >> mlx5_core-$(CONFIG_MLX5_FPGA) += fpga/cmd.o fpga/core.o fpga/conn.o >> fpga/sdk.o \ >> - fpga/ipsec.o >> + fpga/ipsec.o wq.o > > I believe we would prefer to move wq.o to mlx5_core-y. > Otherwise you might build it twice. That's not a problem, Kbuild is smart enough to drop duplicate object files that get built into the same module. If you think it's less confusing to readers of this file if it gets put into core, that's fine though, the only downside would be adding a little bit of code bloat for users that want neither the ethernet nor the fpga code (if that is a realistic use case). Arnd