From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Jean Delvare <jdelvare@suse.de>,
Vincent MAILHOL <mailhol.vincent@wanadoo.fr>
Cc: linux-can@vger.kernel.org, kernel@pengutronix.de,
Marc Kleine-Budde <mkl@pengutronix.de>,
Miguel Ojeda <ojeda@kernel.org>,
Masahiro Yamada <masahiroy@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH] can: rockchip_canfd: Drop obsolete dependency on COMPILE_TEST
Date: Tue, 12 Nov 2024 12:15:06 +0100 (CET) [thread overview]
Message-ID: <dcced72-7be1-b44-432a-dac2ad7f4cc6@linux-m68k.org> (raw)
In-Reply-To: <CAMZ6RqJxb-52eSPqvaESjA-Wd_Jd-=gFO1HWbzxWe3gx7GWDmA@mail.gmail.com>
Hi Jean, Vincent,
On Tue, 22 Oct 2024, Vincent MAILHOL wrote:
> On Tue. 22 Oct. 2024 at 20:06, Jean Delvare <jdelvare@suse.de> wrote:
>> Since commit 0166dc11be91 ("of: make CONFIG_OF user selectable"), OF
>> can be enabled on all architectures. Therefore depending on
>> COMPILE_TEST as an alternative is no longer needed.
>
> I understand the motivation behind this patch, but for me, as a
> maintainer, it becomes more work when I want to do a compile test.
> Before I would have needed to only select COMPILE_TEST but now, I
> would need to remember to also select OF for that driver to appear in
> the menuconfig.
IMHO these are two different things: to get a working driver, you need
to enable OF; to do (may be limited, i.e. may not give a working driver)
compile-testing, you need to enable COMPILE_TEST.
So I think commit 51e102ec23b25e6c ("can: rockchip_canfd: Drop obsolete
dependency on COMPILE_TEST") should be reverted.
> Well, I am not strongly against this simplification, but, wouldn't it
> be good to make COMPILE_TEST automatically select OF then? Looking at
> the description of COMPILE_TEST, I read:
>
> If you are a developer and want to build everything available, say Y here.
>
> So having COMPILE_TEST automatically select OF looks sane to me as it
> goes in the direction of "building everything". If this makes sense, I
> can send a patch for this. Thoughts?
Please don't do that! Merely enabling COMPILE_TEST should not enable
any additional code in the kernel.
>> --- linux-6.12-rc4.orig/drivers/net/can/rockchip/Kconfig
>> +++ linux-6.12-rc4/drivers/net/can/rockchip/Kconfig
>> @@ -2,7 +2,7 @@
>>
>> config CAN_ROCKCHIP_CANFD
>> tristate "Rockchip CAN-FD controller"
>> - depends on OF || COMPILE_TEST
>> + depends on OF
>> select CAN_RX_OFFLOAD
>> help
>> Say Y here if you want to use CAN-FD controller found on
>>
Gr{oetje,eeting}s,
Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@linux-m68k.org
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds
next prev parent reply other threads:[~2024-11-12 11:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-22 11:04 [PATCH] can: rockchip_canfd: Drop obsolete dependency on COMPILE_TEST Jean Delvare
2024-10-22 13:22 ` Vincent MAILHOL
2024-10-22 17:04 ` Jean Delvare
2024-10-23 5:20 ` Vincent MAILHOL
2024-11-12 11:15 ` Geert Uytterhoeven [this message]
2024-11-21 13:50 ` Jean Delvare
2024-11-22 14:33 ` Geert Uytterhoeven
2024-11-22 14:36 ` Geert Uytterhoeven
2024-11-25 8:26 ` Jean Delvare
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=dcced72-7be1-b44-432a-dac2ad7f4cc6@linux-m68k.org \
--to=geert@linux-m68k.org \
--cc=akpm@linux-foundation.org \
--cc=jdelvare@suse.de \
--cc=kernel@pengutronix.de \
--cc=linux-can@vger.kernel.org \
--cc=mailhol.vincent@wanadoo.fr \
--cc=masahiroy@kernel.org \
--cc=mkl@pengutronix.de \
--cc=ojeda@kernel.org \
/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