Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
* linux-next: build warning after merge of the powerpc tree
@ 2021-04-14 23:36 Stephen Rothwell
  0 siblings, 0 replies; 10+ messages in thread
From: Stephen Rothwell @ 2021-04-14 23:36 UTC (permalink / raw)
  To: Michael Ellerman, PowerPC
  Cc: Yu Kuai, Linux Kernel Mailing List, Linux Next Mailing List


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

Hi all,

After merging the powerpc tree, today's linux-next build (powerpc
ppc64_defconfig) produced this warning:

drivers/macintosh/via-pmu.c:190:12: warning: '__fake_sleep' defined but not used [-Wunused-variable]
  190 | static int __fake_sleep;
      |            ^~~~~~~~~~~~

Introduced by commit

  95d143923379 ("macintosh/via-pmu: Make some symbols static")

-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: linux-next: build warning after merge of the powerpc tree
  2021-04-15  8:52 Stephen Rothwell
@ 2021-04-16 10:54 ` Michael Ellerman
  0 siblings, 0 replies; 10+ messages in thread
From: Michael Ellerman @ 2021-04-16 10:54 UTC (permalink / raw)
  To: Stephen Rothwell, PowerPC
  Cc: Shivaprasad G Bhat, Linux Kernel Mailing List, Linux Next Mailing List

Stephen Rothwell <sfr@canb.auug.org.au> writes:
> Hi all,
>
> After merging the powerpc tree, today's linux-next build (powerpc
> allyesconfig) produced this warning:
>
> In file included from include/linux/device.h:15,
>                  from arch/powerpc/include/asm/io.h:27,
>                  from include/linux/io.h:13,
>                  from include/linux/irq.h:20,
>                  from arch/powerpc/include/asm/hardirq.h:6,
>                  from include/linux/hardirq.h:11,
>                  from include/linux/highmem.h:10,
>                  from include/linux/bio.h:8,
>                  from include/linux/libnvdimm.h:14,
>                  from arch/powerpc/platforms/pseries/papr_scm.c:12:
> arch/powerpc/platforms/pseries/papr_scm.c: In function 'papr_scm_pmem_flush':
> arch/powerpc/platforms/pseries/papr_scm.c:144:26: warning: format '%lld' expects argument of type 'long long int', but argument 3 has type 'long int' [-Wformat=]
>   144 |   dev_err(&p->pdev->dev, "flush error: %lld", rc);
>       |                          ^~~~~~~~~~~~~~~~~~~
> include/linux/dev_printk.h:19:22: note: in definition of macro 'dev_fmt'
>    19 | #define dev_fmt(fmt) fmt
>       |                      ^~~
> arch/powerpc/platforms/pseries/papr_scm.c:144:3: note: in expansion of macro 'dev_err'
>   144 |   dev_err(&p->pdev->dev, "flush error: %lld", rc);
>       |   ^~~~~~~
> arch/powerpc/platforms/pseries/papr_scm.c:144:43: note: format string is defined here
>   144 |   dev_err(&p->pdev->dev, "flush error: %lld", rc);
>       |                                        ~~~^
>       |                                           |
>       |                                           long long int
>       |                                        %ld
>
> Introduced by commit
>
>   75b7c05ebf90 ("powerpc/papr_scm: Implement support for H_SCM_FLUSH hcall")

My bad.

cheers

^ permalink raw reply	[flat|nested] 10+ messages in thread

* linux-next: build warning after merge of the powerpc tree
@ 2021-04-15  8:52 Stephen Rothwell
  2021-04-16 10:54 ` Michael Ellerman
  0 siblings, 1 reply; 10+ messages in thread
From: Stephen Rothwell @ 2021-04-15  8:52 UTC (permalink / raw)
  To: Michael Ellerman, PowerPC
  Cc: Shivaprasad G Bhat, Linux Kernel Mailing List, Linux Next Mailing List


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

Hi all,

After merging the powerpc tree, today's linux-next build (powerpc
allyesconfig) produced this warning:

In file included from include/linux/device.h:15,
                 from arch/powerpc/include/asm/io.h:27,
                 from include/linux/io.h:13,
                 from include/linux/irq.h:20,
                 from arch/powerpc/include/asm/hardirq.h:6,
                 from include/linux/hardirq.h:11,
                 from include/linux/highmem.h:10,
                 from include/linux/bio.h:8,
                 from include/linux/libnvdimm.h:14,
                 from arch/powerpc/platforms/pseries/papr_scm.c:12:
arch/powerpc/platforms/pseries/papr_scm.c: In function 'papr_scm_pmem_flush':
arch/powerpc/platforms/pseries/papr_scm.c:144:26: warning: format '%lld' expects argument of type 'long long int', but argument 3 has type 'long int' [-Wformat=]
  144 |   dev_err(&p->pdev->dev, "flush error: %lld", rc);
      |                          ^~~~~~~~~~~~~~~~~~~
include/linux/dev_printk.h:19:22: note: in definition of macro 'dev_fmt'
   19 | #define dev_fmt(fmt) fmt
      |                      ^~~
arch/powerpc/platforms/pseries/papr_scm.c:144:3: note: in expansion of macro 'dev_err'
  144 |   dev_err(&p->pdev->dev, "flush error: %lld", rc);
      |   ^~~~~~~
arch/powerpc/platforms/pseries/papr_scm.c:144:43: note: format string is defined here
  144 |   dev_err(&p->pdev->dev, "flush error: %lld", rc);
      |                                        ~~~^
      |                                           |
      |                                           long long int
      |                                        %ld

Introduced by commit

  75b7c05ebf90 ("powerpc/papr_scm: Implement support for H_SCM_FLUSH hcall")

-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 10+ messages in thread

* linux-next: build warning after merge of the powerpc tree
@ 2019-11-13 22:34 Stephen Rothwell
  0 siblings, 0 replies; 10+ messages in thread
From: Stephen Rothwell @ 2019-11-13 22:34 UTC (permalink / raw)
  To: Michael Ellerman, PowerPC
  Cc: Linux Next Mailing List, Linux Kernel Mailing List, Nayna Jain,
	Eric Richter


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

Hi all,

After merging the powerpc tree, today's linux-next build (x86_64
allmodconfig) produced this warning:

security/integrity/platform_certs/load_uefi.c:17:19: warning: 'efi_cert_sha256_guid' defined but not used [-Wunused-variable]
   17 | static efi_guid_t efi_cert_sha256_guid __initdata = EFI_CERT_SHA256_GUID;
      |                   ^~~~~~~~~~~~~~~~~~~~
security/integrity/platform_certs/load_uefi.c:15:19: warning: 'efi_cert_x509_sha256_guid' defined but not used [-Wunused-variable]
   15 | static efi_guid_t efi_cert_x509_sha256_guid __initdata =
      |                   ^~~~~~~~~~~~~~~~~~~~~~~~~
security/integrity/platform_certs/load_uefi.c:14:19: warning: 'efi_cert_x509_guid' defined but not used [-Wunused-variable]
   14 | static efi_guid_t efi_cert_x509_guid __initdata = EFI_CERT_X509_GUID;
      |                   ^~~~~~~~~~~~~~~~~~

Introduced by commit

  ad723674d675 ("x86/efi: move common keyring handler functions to new file")

-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: linux-next: build warning after merge of the powerpc tree
  2017-09-04  8:53 Stephen Rothwell
@ 2017-09-04  8:59 ` Cédric Le Goater
  0 siblings, 0 replies; 10+ messages in thread
From: Cédric Le Goater @ 2017-09-04  8:59 UTC (permalink / raw)
  To: Stephen Rothwell, Michael Ellerman, Benjamin Herrenschmidt, PowerPC
  Cc: Linux-Next Mailing List, Linux Kernel Mailing List

On 09/04/2017 10:53 AM, Stephen Rothwell wrote:
> Hi all,
> 
> After merging the powerpc tree, today's linux-next build (powerpc
> allyesconfig) produced this warning:
> 
> WARNING: vmlinux.o(.text+0xa7cb8): Section mismatch in reference from the function .xive_spapr_init() to the function .init.text:.xive_core_init()
> The function .xive_spapr_init() references
> the function __init .xive_core_init().
> This is often because .xive_spapr_init lacks a __init 
> annotation or the annotation of .xive_core_init is wrong.
> 
> Introduced by commit
> 
>   eac1e731b59e ("powerpc/xive: guest exploitation of the XIVE interrupt controller")
> 

yes. I just sent a patch for this :

	http://patchwork.ozlabs.org/patch/809542/

Cheers,

C.

^ permalink raw reply	[flat|nested] 10+ messages in thread

* linux-next: build warning after merge of the powerpc tree
@ 2017-09-04  8:53 Stephen Rothwell
  2017-09-04  8:59 ` Cédric Le Goater
  0 siblings, 1 reply; 10+ messages in thread
From: Stephen Rothwell @ 2017-09-04  8:53 UTC (permalink / raw)
  To: Michael Ellerman, Benjamin Herrenschmidt, PowerPC
  Cc: Linux-Next Mailing List, Linux Kernel Mailing List,
	Cédric Le Goater

Hi all,

After merging the powerpc tree, today's linux-next build (powerpc
allyesconfig) produced this warning:

WARNING: vmlinux.o(.text+0xa7cb8): Section mismatch in reference from the function .xive_spapr_init() to the function .init.text:.xive_core_init()
The function .xive_spapr_init() references
the function __init .xive_core_init().
This is often because .xive_spapr_init lacks a __init 
annotation or the annotation of .xive_core_init is wrong.

Introduced by commit

  eac1e731b59e ("powerpc/xive: guest exploitation of the XIVE interrupt controller")

-- 
Cheers,
Stephen Rothwell

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: linux-next: build warning after merge of the powerpc tree
  2015-10-20 10:06 ` Michael Ellerman
@ 2015-10-20 20:45   ` Stephen Rothwell
  0 siblings, 0 replies; 10+ messages in thread
From: Stephen Rothwell @ 2015-10-20 20:45 UTC (permalink / raw)
  To: Michael Ellerman
  Cc: Benjamin Herrenschmidt, linuxppc-dev, linux-next, linux-kernel,
	Denis Kirjanov

Hi Michael,

On Tue, 20 Oct 2015 21:06:51 +1100 Michael Ellerman <mpe@ellerman.id.au> wrote:
>
> On Tue, 2015-10-20 at 16:21 +1100, Stephen Rothwell wrote:
> 
> > After merging the powerpc tree, today's linux-next build (powerpc
> > allyesconfig) produced this warning:
> > 
> > WARNING: vmlinux.o(.text+0x9367c): Section mismatch in reference from the function .msi_bitmap_alloc() to the function .init.text:.memblock_virt_alloc_try_nid()
> > The function .msi_bitmap_alloc() references
> > the function __init .memblock_virt_alloc_try_nid().
> > This is often because .msi_bitmap_alloc lacks a __init
> > annotation or the annotation of .memblock_virt_alloc_try_nid is wrong.
> > 
> > Introduced (probably) by commit
> > 
> >   cb2d3883c603 ("powerpc/msi: Free the bitmap if it was slab allocated")  
> 
> Yeah that's correct, though it should be safe in practice.
> 
> I'm not sure why you only saw that now though, the patch has been in next since
> the 13th of October.

I don't always notice new warnings immediately among all the others :-(

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

^ permalink raw reply	[flat|nested] 10+ messages in thread

* Re: linux-next: build warning after merge of the powerpc tree
  2015-10-20  5:21 Stephen Rothwell
@ 2015-10-20 10:06 ` Michael Ellerman
  2015-10-20 20:45   ` Stephen Rothwell
  0 siblings, 1 reply; 10+ messages in thread
From: Michael Ellerman @ 2015-10-20 10:06 UTC (permalink / raw)
  To: Stephen Rothwell, Benjamin Herrenschmidt, linuxppc-dev
  Cc: linux-next, linux-kernel, Denis Kirjanov

On Tue, 2015-10-20 at 16:21 +1100, Stephen Rothwell wrote:

> Hi all,
> 
> After merging the powerpc tree, today's linux-next build (powerpc
> allyesconfig) produced this warning:
> 
> WARNING: vmlinux.o(.text+0x9367c): Section mismatch in reference from the function .msi_bitmap_alloc() to the function .init.text:.memblock_virt_alloc_try_nid()
> The function .msi_bitmap_alloc() references
> the function __init .memblock_virt_alloc_try_nid().
> This is often because .msi_bitmap_alloc lacks a __init
> annotation or the annotation of .memblock_virt_alloc_try_nid is wrong.
> 
> Introduced (probably) by commit
> 
>   cb2d3883c603 ("powerpc/msi: Free the bitmap if it was slab allocated")


Yeah that's correct, though it should be safe in practice.

I'm not sure why you only saw that now though, the patch has been in next since
the 13th of October.

cheers

^ permalink raw reply	[flat|nested] 10+ messages in thread

* linux-next: build warning after merge of the powerpc tree
@ 2015-10-20  5:21 Stephen Rothwell
  2015-10-20 10:06 ` Michael Ellerman
  0 siblings, 1 reply; 10+ messages in thread
From: Stephen Rothwell @ 2015-10-20  5:21 UTC (permalink / raw)
  To: Michael Ellerman, Benjamin Herrenschmidt, linuxppc-dev
  Cc: linux-next, linux-kernel, Denis Kirjanov

Hi all,

After merging the powerpc tree, today's linux-next build (powerpc
allyesconfig) produced this warning:

WARNING: vmlinux.o(.text+0x9367c): Section mismatch in reference from the function .msi_bitmap_alloc() to the function .init.text:.memblock_virt_alloc_try_nid()
The function .msi_bitmap_alloc() references
the function __init .memblock_virt_alloc_try_nid().
This is often because .msi_bitmap_alloc lacks a __init
annotation or the annotation of .memblock_virt_alloc_try_nid is wrong.

Introduced (probably) by commit

  cb2d3883c603 ("powerpc/msi: Free the bitmap if it was slab allocated")

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

^ permalink raw reply	[flat|nested] 10+ messages in thread

* linux-next: build warning after merge of the powerpc tree
@ 2011-05-19  3:19 Stephen Rothwell
  0 siblings, 0 replies; 10+ messages in thread
From: Stephen Rothwell @ 2011-05-19  3:19 UTC (permalink / raw)
  To: Benjamin Herrenschmidt, Paul Mackerras, linuxppc-dev
  Cc: linux-next, linux-kernel


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

Hi all,

After merging the powerpc tree, today's linux-next build (powerpc
allyesconfig) produced this warning:

WARNING: arch/powerpc/sysdev/built-in.o(.text+0x10eb8): Section mismatch in reference from the function .ics_rtas_init() to the function .init.text:.xics_register_ics()
The function .ics_rtas_init() references
the function __init .xics_register_ics().
This is often because .ics_rtas_init lacks a __init 
annotation or the annotation of .xics_register_ics is wrong.

Introduced by commit 0b05ac6e2480 ("powerpc/xics: Rewrite XICS driver").

ics_rtas_init() is only called from xics_init() which is marked __init,
so ics_rtas_init() should be as well.

-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au
http://www.canb.auug.org.au/~sfr/

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

^ permalink raw reply	[flat|nested] 10+ messages in thread

end of thread, back to index

Thread overview: 10+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-04-14 23:36 linux-next: build warning after merge of the powerpc tree Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2021-04-15  8:52 Stephen Rothwell
2021-04-16 10:54 ` Michael Ellerman
2019-11-13 22:34 Stephen Rothwell
2017-09-04  8:53 Stephen Rothwell
2017-09-04  8:59 ` Cédric Le Goater
2015-10-20  5:21 Stephen Rothwell
2015-10-20 10:06 ` Michael Ellerman
2015-10-20 20:45   ` Stephen Rothwell
2011-05-19  3:19 Stephen Rothwell

Linux-Next Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/linux-next/0 linux-next/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-next linux-next/ https://lore.kernel.org/linux-next \
		linux-next@vger.kernel.org
	public-inbox-index linux-next

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.linux-next


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git