From: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: linux-can@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 3/3] can: tscan1: Kconfig: add COMPILE_TEST
Date: Tue, 15 Jul 2025 20:02:53 +0900 [thread overview]
Message-ID: <e25e9ad6-592d-47f5-bf8b-ac3f0bfde46c@wanadoo.fr> (raw)
In-Reply-To: <20250715-mindful-terrestrial-kangaroo-fc81a1-mkl@pengutronix.de>
On 15/07/2025 at 18:13, Marc Kleine-Budde wrote:
> On 13.07.2025 17:02:45, Vincent Mailhol wrote:
>> tscan1 depends on ISA. Add COMPILE_TEST so that this driver can also be
>> built on other platforms.
>>
>> Signed-off-by: Vincent Mailhol <mailhol.vincent@wanadoo.fr>
>> ---
>> drivers/net/can/sja1000/Kconfig | 2 +-
>> 1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/drivers/net/can/sja1000/Kconfig b/drivers/net/can/sja1000/Kconfig
>> index 2f516cc6d22c4028b1de383baa6b3d3a7605b791..fee9d6f84f5fb9d6a81df00be9d216219723a854 100644
>> --- a/drivers/net/can/sja1000/Kconfig
>> +++ b/drivers/net/can/sja1000/Kconfig
>> @@ -105,7 +105,7 @@ config CAN_SJA1000_PLATFORM
>>
>> config CAN_TSCAN1
>> tristate "TS-CAN1 PC104 boards"
>> - depends on ISA
>> + depends on ISA || COMPILE_TEST
>> help
>> This driver is for Technologic Systems' TSCAN-1 PC104 boards.
>> https://www.embeddedts.com/products/TS-CAN1
>>
>
> What about making it:
>
> --- a/drivers/net/can/sja1000/Kconfig
> +++ b/drivers/net/can/sja1000/Kconfig
> @@ -105,7 +105,7 @@ config CAN_SJA1000_PLATFORM
>
> config CAN_TSCAN1
> tristate "TS-CAN1 PC104 boards"
> - depends on ISA
> + depends on ISA || (COMPILE_TEST && HAS_IOPORT)
> help
> This driver is for Technologic Systems' TSCAN-1 PC104 boards.
> https://www.embeddedts.com/products/TS-CAN1
Yes, I was thinking of the exact same thing after seeing the bot's error
message. I just did not yet find some time to test.
The kernel test robot actually gives instructions on how to reproduce, but for
some reasons which I have not yet troubleshot, it did not work on first try on
my machine.
Well, you know what, because we reached the same conclusion, allow me to be a
bit lazy here. I will just send the v2 and let the bot test it for me.
Yours sincerely,
Vincent Mailhol
prev parent reply other threads:[~2025-07-15 11:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-13 8:02 [PATCH 0/3] can: Kconfig: add missing COMPILE_TEST Vincent Mailhol
2025-07-13 8:02 ` [PATCH 1/3] can: ti_hecc: fix -Woverflow compiler warning Vincent Mailhol
2025-07-13 8:02 ` [PATCH 2/3] can: ti_hecc: Kconfig: add COMPILE_TEST Vincent Mailhol
2025-07-13 8:02 ` [PATCH 3/3] can: tscan1: " Vincent Mailhol
2025-07-14 7:40 ` kernel test robot
2025-07-15 9:13 ` Marc Kleine-Budde
2025-07-15 11:02 ` 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=e25e9ad6-592d-47f5-bf8b-ac3f0bfde46c@wanadoo.fr \
--to=mailhol.vincent@wanadoo.fr \
--cc=linux-can@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkl@pengutronix.de \
/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
all inboxes | Powered by JetHome®