linux-next: build failure after merge of the mips tree

linux-next: build failure after merge of the mips tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 408 bytes --]

Hi all,

After merging the mips tree, today's linux-next build (mips gpr_defconfig)
failed like this:

arch/mips/alchemy/common/setup.c:99:9: error: implicit declaration of function ‘remap_pfn_range’; did you mean ‘io_remap_pfn_range’? [-Werror=implicit-function-declaration]

Caused by commit

  d399157283fb ("MIPS: cleanup fixup_bigphys_addr handling")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

Re: linux-next: build failure after merge of the mips tree

[Thomas Bogendoerfer]

On Mon, Apr 20, 2020 at 08:07:44PM +1000, Stephen Rothwell wrote:
> After merging the mips tree, today's linux-next build (mips gpr_defconfig)
> failed like this:
> 
> arch/mips/alchemy/common/setup.c:99:9: error: implicit declaration of function ‘remap_pfn_range’; did you mean ‘io_remap_pfn_range’? [-Werror=implicit-function-declaration]
> 
> Caused by commit
> 
>   d399157283fb ("MIPS: cleanup fixup_bigphys_addr handling")

I've pushed a fix to mips-next branch.

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

Re: linux-next: build failure after merge of the mips tree

[Thomas Bogendoerfer]

On Mon, Mar 27, 2023 at 04:12:17PM +1100, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the mips tree, today's linux-next build (mips
> cavium_octeon_defconfig) failed like this:
> 
> arch/mips/cavium-octeon/octeon-irq.c:2893:35: error: assignment to ‘u64’ {aka ‘long long unsigned int’} from ‘void *’ makes integer from pointer without a cast [-Werror=int-conversion]
> 
> (reported here: https://linux.kernelci.org/build/id/6420fc4409ffd05fb69c951a/logs/)
> 
> Caused by commit
> 
>   ed6a0b6e9fd7 ("MIPS: octeon: Use of_address_to_resource()")

I've added below patch to fix the problem.

Thomas.

commit 101f26c72825c5dba1dfe826e4202a9a04b435c6
Author: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
Date:   Mon Mar 27 10:35:22 2023 +0200

    MIPS: octeon: Fix compile error
    
    Commit ed6a0b6e9fd7 ("MIPS: octeon: Use of_address_to_resource()") lost
    a cast, which causes a compile error.
    
    Fixes: ed6a0b6e9fd7 ("MIPS: octeon: Use of_address_to_resource()")
    Signed-off-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>

diff --git a/arch/mips/cavium-octeon/octeon-irq.c b/arch/mips/cavium-octeon/octeon-irq.c
index 064e2409377a..8425a6b38aa2 100644
--- a/arch/mips/cavium-octeon/octeon-irq.c
+++ b/arch/mips/cavium-octeon/octeon-irq.c
@@ -2890,7 +2890,7 @@ static int __init octeon_irq_init_ciu3(struct device_node *ciu_node,
 	if (WARN_ON(ret))
 		return ret;
 
-	ciu3_info->ciu3_addr = base_addr = phys_to_virt(res.start);
+	ciu3_info->ciu3_addr = base_addr = (u64)phys_to_virt(res.start);
 	ciu3_info->node = node;
 
 	consts.u64 = cvmx_read_csr(base_addr + CIU3_CONST);


-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea.                                                [ RFC1925, 2.3 ]

linux-next: build failure after merge of the mips tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 522 bytes --]

Hi all,

After merging the mips tree, today's linux-next build (mips
cavium_octeon_defconfig) failed like this:

arch/mips/cavium-octeon/octeon-irq.c:2893:35: error: assignment to ‘u64’ {aka ‘long long unsigned int’} from ‘void *’ makes integer from pointer without a cast [-Werror=int-conversion]

(reported here: https://linux.kernelci.org/build/id/6420fc4409ffd05fb69c951a/logs/)

Caused by commit

  ed6a0b6e9fd7 ("MIPS: octeon: Use of_address_to_resource()")

-- 
Cheers,
Stephen Rothwell

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

linux-next: build failure after merge of the mips tree

[Thierry Reding]

Today's linux-next merge fails to build on various default configuration
builds. This seems to be caused by the following commit:

	5395d97 MIPS: Fix start of free memory when using initrd

Looking at the patchwork URLs in that commit message, Greg's original
patch seems to have been fine, but Ashok's patch uses the initrd_end
symbol outside of the section protected by an CONFIG_BLK_DEV_INITRD
#ifdef and therefore causes to fail during linking.

I've reverted the patch in today's linux-next tree.

Thierry

Re: linux-next: build failure after merge of the mips tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 646 bytes --]

Hi Ralf,

On Mon, 18 Feb 2013 10:43:40 +1100 Stephen Rothwell <sfr@canb.auug.org.au> wrote:
>
> After merging the mips tree, today's linux-next build (x86_64
> allmodconfig) failed like this:
> 
> drivers/ssb/driver_gpio.c: In function 'ssb_gpio_chipco_to_irq':
> drivers/ssb/driver_gpio.c:82:3: error: implicit declaration of function 'ssb_mips_irq' [-Werror=implicit-function-declaration]
> 
> Caused by commit d630dd4ef20f ("ssb: add gpio_to_irq again").
> 
> I have used the mips tree from next-20130215 for today.

I am still getting this build problem.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

Re: linux-next: build failure after merge of the mips tree

[Hauke Mehrtens]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 02/18/2013 12:43 AM, Stephen Rothwell wrote:
> Hi Ralf,
> 
> After merging the mips tree, today's linux-next build (x86_64 
> allmodconfig) failed like this:
> 
> drivers/ssb/driver_gpio.c: In function 'ssb_gpio_chipco_to_irq': 
> drivers/ssb/driver_gpio.c:82:3: error: implicit declaration of
> function 'ssb_mips_irq' [-Werror=implicit-function-declaration]
> 
> Caused by commit d630dd4ef20f ("ssb: add gpio_to_irq again").
> 
> I have used the mips tree from next-20130215 for today.
> 
Hi Ralf and blogic,

Could you drop this patch [0] and this one [1].

I saw that they are not any more in blogic tree.

Hauke

[0]: https://patchwork.linux-mips.org/patch/4719/
[1]: https://patchwork.linux-mips.org/patch/4720/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with undefined - http://www.enigmail.net/

iQIcBAEBAgAGBQJRIW7SAAoJEIZ0px9YPRMySfMQAII6ZFgh+dDS/gEhxCmZ5EJZ
dmz5AjafHmmqAKuw5j5erKvRzocxaxwLscvEjv6WXD/dGD7DoUkixSkoHD0G5ptE
gba3OL8qqBQGzuqhUsfKCnYS3b7UGYC95G9qS03jcikm46Rl3ufpEnOswkIwyssw
Qd0yVqvsmXDaTz6LljwSYGT6BxLo63QmoaxH64yCXwYtOh+vGanif8U+QZcg61Hm
jL1CRlbzjJg5VrtTOak9SVsRFRp4TOvJe7TI5P/Nm20mkt6q+1sWcoOXa1egG0k7
68Y2hTzlERTK6LCpmHRZcQxXPbMl/KP03+mgtqcN5xQtkGq4NfcnfG0HIANo9fpf
BlnCX//gDaLRVcwlQnAShVYRcLd+tjb6l+2ObYLShJVFPdD5YJ3sTiySKW7xVW04
iFlzxDWKYA2NILHldHHa+MX7r86IBPLrZhG+IqgdjLcw4zQZiGn2heVSQipzmPGm
eBWqJuSUtVYNrEFVd/+CcqHo5jvmqmybh7+DLi6fVBvNb1vh9ApmltVuD37T00CB
d3bOF5VEFQR+zoNloxriI84SCZPRu/in8f/Bqy9x+iGnkgW+FxnJnDi4kEaerNB7
jjZow64JwE5f/pYHle/ffLUvsCRLV7GpvJ33n4OxFQyVMYHrPEdbF2r+YkytA5zJ
KzZDEk6WfzVItcPcjSTg
=EwXd
-----END PGP SIGNATURE-----

linux-next: build failure after merge of the mips tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 500 bytes --]

Hi Ralf,

After merging the mips tree, today's linux-next build (x86_64
allmodconfig) failed like this:

drivers/ssb/driver_gpio.c: In function 'ssb_gpio_chipco_to_irq':
drivers/ssb/driver_gpio.c:82:3: error: implicit declaration of function 'ssb_mips_irq' [-Werror=implicit-function-declaration]

Caused by commit d630dd4ef20f ("ssb: add gpio_to_irq again").

I have used the mips tree from next-20130215 for today.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

linux-next: build failure after merge of the mips tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 1127 bytes --]

Hi Ralf,

After merging the mips tree, today's linux-next build (x86_64
allmodconfig) failed like this:

warning: (SND_SOC_DB1200) selects SND_SOC_AU1XPSC which has unmet direct dependencies (SOUND && !M68K && !UML && SND && SND_SOC && MIPS_ALCHEMY)
warning: (SND_SOC_DB1200) selects SND_SOC_AU1XPSC which has unmet direct dependencies (SOUND && !M68K && !UML && SND && SND_SOC && MIPS_ALCHEMY)
sound/soc/au1x/psc-ac97.c:26:36: fatal error: asm/mach-au1x00/au1000.h: No such file or directory
compilation terminated.
sound/soc/au1x/db1200.c:16:36: fatal error: asm/mach-au1x00/au1000.h: No such file or directory
compilation terminated.
sound/soc/au1x/psc-i2s.c:24:36: fatal error: asm/mach-au1x00/au1000.h: No such file or directory
compilation terminated.
sound/soc/au1x/dbdma2.c:27:36: fatal error: asm/mach-au1x00/au1000.h: No such file or directory

[I left the Kconfig lines there just in case they are relevant]

Probably caused by some Kconfig dependency/select change.

I have used the mips tree form next-20111109 for today.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]

linux-next: build failure after merge of the mips tree

[Stephen Rothwell]

[-- Attachment #1: Type: text/plain, Size: 900 bytes --]

Hi Ralf,

After merging the xtensa tree, today's linux-next build (x86_64
allmodconfig) failed like this:

drivers/video/jz4740_fb.c:29:39: error: asm/mach-jz4740/jz4740_fb.h: No such file or directory
drivers/video/jz4740_fb.c:30:34: error: asm/mach-jz4740/gpio.h: No such file or directory
drivers/video/jz4740_fb.c:149: error: array type has incomplete element type
drivers/video/jz4740_fb.c:150: error: implicit declaration of function 'JZ_GPIO_BULK_PIN'
drivers/video/jz4740_fb.c:150: error: 'LCD_PCLK' undeclared here (not in a function)

... and on and on ...

Caused by commit e457478bc296ea3f2ae51ca7c165a59621c1655d ("FBDEV:
JZ4740: Add framebuffer driver").  Presumably this driver will only build
on MIPS?

I have used the mips tree from next-20100726 for today.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 490 bytes --]