Received: by 2002:a6b:500f:0:0:0:0:0 with SMTP id e15csp1461947iob; Sat, 14 May 2022 09:34:46 -0700 (PDT) X-Google-Smtp-Source: ABdhPJzDTH6SKdlK46DMIplDqxOQTIPiZQfkiIptAzy73RaFlOUO5qjcN0bxMEFUT5StslXCeU5h X-Received: by 2002:a05:6000:1786:b0:20c:6063:5014 with SMTP id e6-20020a056000178600b0020c60635014mr8218764wrg.251.1652546086005; Sat, 14 May 2022 09:34:46 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1652546085; cv=none; d=google.com; s=arc-20160816; b=pPM8X76S2aTvnh7+9NilLyJLBSvsNmdZUg1YUOaWaot0LXOeiL6/9+xD6AUd2M+RYC QrnE/GVYYkTOm60pGKFdaBmZ9z5Y2F//VOBdBsUX3i6fZXkFfdsCjmbqEX01oLe5s6Ci 9I+PxOXqFNzd8ePIp5UMkbL/b5QyQHI27Bf8ggZvAa0zLBcmD081wsglSD9+HBAlF5pD ZI/YWkActxagjMx7nzP1kKSMbuxlUnW1r45QhE9absE2/GKTTJt8pym4qkQ6l2SEAlB6 WjnWyG+qOOMZSJDNhbJrJ8CLULFfRGkmlJsPv0jnlq33lEddQbBGrCughUkBg8L2NbzH L/iw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date; bh=Aq6mBpAj3a1sdEl5UrfrrtVcXIx70gAAcOK6NbJpCWs=; b=DB7uBAF/o2mwss77oZVkhN85WzBT3g7P/tc/lP/Irzx+/ROl+0FofNV8kPymB0+9yi he45SFDInNU7blqMJK6iyMu/IYbZ1G8RgryYusE7aW0tmjrKBuPPUKPO/vgCqS1lP/gS kU4aJaGThnVU2OwZBFeo2PuS3t+acqN/ozcm4gJkToV/RsT9GnjKJNUFauzWRHseXcAI N0VG6FCByoRb2Pu6myoa0zfVNLq/Ur9UUAe1hhm11v9tjbaSh16nRG4aS8pMOLPb4+zl vWXlNyho+ZqT+e1X+120zsnLymBEpxsr5pkltNcXBwo6OveLEV8sp7FWbpVgScv/VL6S Crhw== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id z16-20020a7bc150000000b003944b028d03si8852714wmi.60.2022.05.14.09.34.18; Sat, 14 May 2022 09:34:45 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230286AbiENLRd (ORCPT + 99 others); Sat, 14 May 2022 07:17:33 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49398 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229449AbiENLRc (ORCPT ); Sat, 14 May 2022 07:17:32 -0400 Received: from mail.enpas.org (zhong.enpas.org [IPv6:2a03:4000:2:537::1]) by lindbergh.monkeyblade.net (Postfix) with ESMTP id 27E7D21AD; Sat, 14 May 2022 04:17:30 -0700 (PDT) Received: from [127.0.0.1] (localhost [127.0.0.1]) by mail.enpas.org (Postfix) with ESMTPSA id A8421FF959; Sat, 14 May 2022 11:17:29 +0000 (UTC) Date: Sat, 14 May 2022 13:17:26 +0200 From: Max Staudt To: Vincent MAILHOL Cc: kernel test robot , Marc Kleine-Budde , llvm@lists.linux.dev, kbuild-all@lists.01.org, linux-can@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2 1/2] can: skb:: move can_dropped_invalid_skb and can_skb_headroom_valid to skb.c Message-ID: <20220514131726.55fbbcdb.max@enpas.org> In-Reply-To: References: <20220513153606.302464-2-mailhol.vincent@wanadoo.fr> <202205141221.H0aZXRak-lkp@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_NONE, SPF_PASS,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat, 14 May 2022 14:16:09 +0900 Vincent MAILHOL wrote: > OK, so the issue is that VCAN and VXCAN are users of > can_dropped_invalid_skb() but do not depend on CAN_DEV. Above error > will appear if CONFIG_CAN_DEV is not set (or if CONFIG_V{,X}CAN is set > to "yes" and CAN_DEV is set to "module"). > I see three choices here: > 1. move can_dropped_invalid_skb() outside of drivers/net/can (i.e. > move it somewhere in net/can). > 2. split CAN_DEV into one additional sub module: CAN_SKB and add a > dependency to it in VCAN and VXCAN. > 3. Add a dependency to CAN_DEV in VCAN and VXCAN > > 1. is I think the worse, 2. the best, 3. is the laziest option and is > kind of acceptable. > @Marc (and anyone else), what are your thoughts? I think that having v(x)can depend on can-dev isn't half bad - for the user, they are CAN devices, anyway, and modprobe does the dependency resolution magic. Splitting into too many modules is something I'd avoid because of the overhead involved. Max