Linux CAN drivers development
 help / color / mirror / Atom feed
From: Pavel Pisa <pisa@cmp.felk.cvut.cz>
To: Jean Delvare <jdelvare@suse.de>
Cc: linux-can@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>,
	Ondrej Ille <ondrej.ille@gmail.com>
Subject: Re: [PATCH] can: ctucanfd: Drop obsolete dependency on COMPILE_TEST
Date: Thu, 24 Nov 2022 15:56:38 +0100	[thread overview]
Message-ID: <202211241556.38957.pisa@cmp.felk.cvut.cz> (raw)
In-Reply-To: <20221124141604.4265225f@endymion.delvare>

Thanks for the care. I cannot judge change on my personal opinion.
But if that is general direction even for other drivers
then I confirm the change.

On Thursday 24 of November 2022 14:16:04 Jean Delvare wrote:
> Since commit 0166dc11be91 ("of: make CONFIG_OF user selectable"), it
> is possible to test-build any driver which depends on OF on any
> architecture by explicitly selecting OF. Therefore depending on
> COMPILE_TEST as an alternative is no longer needed.
>
> It is actually better to always build such drivers with OF enabled,
> so that the test builds are closer to how each driver will actually be
> built on its intended target. Building them without OF may not test
> much as the compiler will optimize out potentially large parts of the
> code. In the worst case, this could even pop false positive warnings.
> Dropping COMPILE_TEST here improves the quality of our testing and
> avoids wasting time on non-existent issues.
>
> Signed-off-by: Jean Delvare <jdelvare@suse.de>
> Cc: Pavel Pisa <pisa@cmp.felk.cvut.cz>
> Cc: Ondrej Ille <ondrej.ille@gmail.com>
> ---
>  drivers/net/can/ctucanfd/Kconfig |    2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> --- linux-6.0.orig/drivers/net/can/ctucanfd/Kconfig
> +++ linux-6.0/drivers/net/can/ctucanfd/Kconfig
> @@ -23,7 +23,7 @@ config CAN_CTUCANFD_PCI
>
>  config CAN_CTUCANFD_PLATFORM
>  	tristate "CTU CAN-FD IP core platform (FPGA, SoC) driver"
> -	depends on HAS_IOMEM && (OF || COMPILE_TEST)
> +	depends on HAS_IOMEM && OF
>  	select CAN_CTUCANFD
>  	help
>  	  The core has been tested together with OpenCores SJA1000



  reply	other threads:[~2022-11-24 15:06 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-24 13:16 [PATCH] can: ctucanfd: Drop obsolete dependency on COMPILE_TEST Jean Delvare
2022-11-24 14:56 ` Pavel Pisa [this message]
2022-11-25 15:57   ` Marc Kleine-Budde
2022-11-27  8:09     ` Pavel Pisa
2022-11-30 10:23       ` Marc Kleine-Budde
2022-11-30 10:26 ` Marc Kleine-Budde

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=202211241556.38957.pisa@cmp.felk.cvut.cz \
    --to=pisa@cmp.felk.cvut.cz \
    --cc=jdelvare@suse.de \
    --cc=linux-can@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ondrej.ille@gmail.com \
    /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