public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan Chancellor <nathan@kernel.org>
To: Andi Shyti <andi.shyti@kernel.org>
Cc: linux-i2c <linux-i2c@vger.kernel.org>,
	Khalil Blaiech <kblaiech@nvidia.com>,
	Asmaa Mnebhi <asmaa@nvidia.com>
Subject: Re: [PATCH] i2c: mlxbf: Allow build with COMPILE_TEST
Date: Sat, 10 May 2025 20:50:48 +0100	[thread overview]
Message-ID: <20250510195048.GA1513488@ax162> (raw)
In-Reply-To: <20250505215854.2896383-1-andi.shyti@kernel.org>

On Mon, May 05, 2025 at 11:58:54PM +0200, Andi Shyti wrote:
> Extend the Kconfig dependency to include COMPILE_TEST so the
> Mellanox BlueField I2C driver can be built on non-ARM64 platforms
> for compile testing purposes.
> 
> Signed-off-by: Andi Shyti <andi.shyti@kernel.org>
> Cc: Khalil Blaiech <kblaiech@nvidia.com>
> Cc: Asmaa Mnebhi <asmaa@nvidia.com>
> ---
>  drivers/i2c/busses/Kconfig | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/drivers/i2c/busses/Kconfig b/drivers/i2c/busses/Kconfig
> index adb2910525b1..9f216d5db91d 100644
> --- a/drivers/i2c/busses/Kconfig
> +++ b/drivers/i2c/busses/Kconfig
> @@ -855,7 +855,7 @@ config I2C_LS2X
>  
>  config I2C_MLXBF
>          tristate "Mellanox BlueField I2C controller"
> -        depends on MELLANOX_PLATFORM && ARM64
> +        depends on (MELLANOX_PLATFORM && ARM64) || COMPILE_TEST
>  	depends on ACPI
>  	select I2C_SLAVE
>          help
> -- 
> 2.49.0
> 

There are 64-bit divides in several places within this driver so this
patch breaks the build on 32-bit platforms when compile testing now:

  i386-linux-ld: drivers/i2c/busses/i2c-mlxbf.o: in function `mlxbf_i2c_calculate_freq_from_tyu':
  i2c-mlxbf.c:(.text+0x3e): undefined reference to `__udivdi3'
  i386-linux-ld: drivers/i2c/busses/i2c-mlxbf.o: in function `mlxbf_i2c_calculate_freq_from_yu':
  i2c-mlxbf.c:(.text+0x8e): undefined reference to `__udivdi3'
  i386-linux-ld: drivers/i2c/busses/i2c-mlxbf.o: in function `mlxbf_i2c_probe':
  i2c-mlxbf.c:(.text+0x1749): undefined reference to `__udivdi3'
  i386-linux-ld: i2c-mlxbf.c:(.text+0x1769): undefined reference to `__udivdi3'
  i386-linux-ld: i2c-mlxbf.c:(.text+0x17c0): undefined reference to `__udivdi3'
  i386-linux-ld: drivers/i2c/busses/i2c-mlxbf.o:i2c-mlxbf.c:(.text+0x17e6): more undefined references to `__udivdi3' follow

Cheers,
Nathan

  parent reply	other threads:[~2025-05-10 19:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-05 21:58 [PATCH] i2c: mlxbf: Allow build with COMPILE_TEST Andi Shyti
2025-05-08 10:10 ` Andi Shyti
2025-05-08 13:40   ` Khalil Blaiech
2025-05-10 19:50 ` Nathan Chancellor [this message]
2025-05-12 22:55   ` Andi Shyti

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=20250510195048.GA1513488@ax162 \
    --to=nathan@kernel.org \
    --cc=andi.shyti@kernel.org \
    --cc=asmaa@nvidia.com \
    --cc=kblaiech@nvidia.com \
    --cc=linux-i2c@vger.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