linux-can.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vincent Mailhol <mailhol@kernel.org>
To: Davide Caratti <dcaratti@redhat.com>,
	Marc Kleine-Budde <mkl@pengutronix.de>,
	linux-can@vger.kernel.org
Cc: Oliver Hartkopp <socketcan@hartkopp.net>,
	Felix Maurer <fmaurer@redhat.com>
Subject: Re: [PATCH v2] selftests: can: enable CONFIG_CAN_VCAN as a module
Date: Tue, 2 Sep 2025 16:41:56 +0900	[thread overview]
Message-ID: <9ccb3940-3432-47b2-a71c-5edb84f6bb0e@kernel.org> (raw)
In-Reply-To: <3424bff9cf34d66633ef410ba506f005a94e310e.1756742645.git.dcaratti@redhat.com>

On 02/09/2025 at 01:07, Davide Caratti wrote:
> A proper kernel configuration for running kselftest can be obtained with:
> 
>  $ yes | make kselftest-merge
> 
> Build of 'vcan' driver is currently missing, while the other required knobs
> are already there because of net/link_netns.py [1]. Add a config file in
> selftests/net/can to store the minimum set of kconfig needed for CAN
> selftests. While at it, move existing CAN-related knobs from selftests/net
> to selftests/net/can.
> 
> [1] https://patch.msgid.link/20250219125039.18024-14-shaw.leon@gmail.com
> 
> V2:
>  - move CAN-related knobs needed by [1] into selftests/net/can (thanks
>    Vincent Mailhol); remove enabling of CAN_RAW and CAN_NETLINK since
>    Kconfig already implies them
> 
> Fixes: 77442ffa83e8 ("selftests: can: Import tst-filter from can-tests")
> Signed-off-by: Davide Caratti <dcaratti@redhat.com>
> ---
>  tools/testing/selftests/net/can/config | 4 ++++
>  tools/testing/selftests/net/config     | 3 ---
>  2 files changed, 4 insertions(+), 3 deletions(-)
>  create mode 100644 tools/testing/selftests/net/can/config
> 
> diff --git a/tools/testing/selftests/net/can/config b/tools/testing/selftests/net/can/config
> new file mode 100644
> index 000000000000..0cb5598eb702
> --- /dev/null
> +++ b/tools/testing/selftests/net/can/config
> @@ -0,0 +1,4 @@
> +CONFIG_CAN=m
> +CONFIG_CAN_DEV=m
> +CONFIG_CAN_VXCAN=m
> +CONFIG_CAN_VCAN=m

One more nitpick: can you also sort the line in alphabetic order?

  CONFIG_CAN=m
  CONFIG_CAN_DEV=m
  CONFIG_CAN_VCAN=m
  CONFIG_CAN_VXCAN=m

(VXCAN after VCAN)

> diff --git a/tools/testing/selftests/net/config b/tools/testing/selftests/net/config
> index c24417d0047b..18bec89c77b9 100644
> --- a/tools/testing/selftests/net/config
> +++ b/tools/testing/selftests/net/config
> @@ -120,9 +120,6 @@ CONFIG_XFRM_USER=m
>  CONFIG_IP_NF_MATCH_RPFILTER=m
>  CONFIG_IP6_NF_MATCH_RPFILTER=m
>  CONFIG_IPVLAN=m
> -CONFIG_CAN=m
> -CONFIG_CAN_DEV=m
> -CONFIG_CAN_VXCAN=m
>  CONFIG_NETKIT=y
>  CONFIG_NET_PKTGEN=m
>  CONFIG_IPV6_ILA=m

Yours sincerely,
Vincent Mailhol


      parent reply	other threads:[~2025-09-02  7:41 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-01 16:07 [PATCH v2] selftests: can: enable CONFIG_CAN_VCAN as a module Davide Caratti
2025-09-02  5:42 ` Vincent Mailhol
2025-09-02  7:41 ` Vincent Mailhol [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=9ccb3940-3432-47b2-a71c-5edb84f6bb0e@kernel.org \
    --to=mailhol@kernel.org \
    --cc=dcaratti@redhat.com \
    --cc=fmaurer@redhat.com \
    --cc=linux-can@vger.kernel.org \
    --cc=mkl@pengutronix.de \
    --cc=socketcan@hartkopp.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).