Linux-Next Archive on lore.kernel.org
 help / color / Atom feed
* linux-next: build warning after merge of the tip tree
@ 2020-03-30  2:47 Stephen Rothwell
  2020-03-31 21:57 ` Stephen Rothwell
  0 siblings, 1 reply; 139+ messages in thread
From: Stephen Rothwell @ 2020-03-30  2:47 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: Linux Next Mailing List, Linux Kernel Mailing List, Al Viro


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

Hi all,

After merging the tip tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:

kernel/futex.c: In function 'do_futex':
kernel/futex.c:1676:17: warning: 'oldval' may be used uninitialized in this function [-Wmaybe-uninitialized]
 1676 |   return oldval == cmparg;
      |          ~~~~~~~^~~~~~~~~
kernel/futex.c:1652:6: note: 'oldval' was declared here
 1652 |  int oldval, ret;
      |      ^~~~~~

Introduced by commit

  a08971e9488d ("futex: arch_futex_atomic_op_inuser() calling conventions change")

but I don't see how it makes this difference :-(

-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2020-11-05  7:06 Stephen Rothwell
  2020-11-06  4:35 ` Stephen Rothwell
  0 siblings, 1 reply; 139+ messages in thread
From: Stephen Rothwell @ 2020-11-05  7:06 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: Balbir Singh, Linux Kernel Mailing List, Linux Next Mailing List


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

Hi all,

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

Documentation/admin-guide/hw-vuln/l1d_flush.rst:25: WARNING: undefined label: documentation/userspace-api/spec_ctrl.rst (if the link has no caption the label must precede a section header)

Introduced by commit

  767d46ab566d ("Documentation: Add L1D flushing Documentation")

-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2020-10-28  3:23 Stephen Rothwell
  2020-11-15 22:17 ` Stephen Rothwell
  2020-11-15 22:23 ` Balbir Singh
  0 siblings, 2 replies; 139+ messages in thread
From: Stephen Rothwell @ 2020-10-28  3:23 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: Balbir Singh, Linux Kernel Mailing List, Linux Next Mailing List


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

Hi all,

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

Documentation/admin-guide/hw-vuln/l1d_flush.rst:25: WARNING: undefined label: documentation/userspace-api/spec_ctrl.rst (if the link has no caption the label must precede a section header)

Introduced by commit

  767d46ab566d ("Documentation: Add L1D flushing Documentation")

-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2020-10-08  4:28 Stephen Rothwell
  2020-10-08  9:02 ` Borislav Petkov
  0 siblings, 1 reply; 139+ messages in thread
From: Stephen Rothwell @ 2020-10-08  4:28 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: Borislav Petkov, Dan Williams, Linux Kernel Mailing List,
	Linux Next Mailing List


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

Hi all,

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

WARNING: modpost: EXPORT symbol "copy_mc_fragile" [vmlinux] version generation failed, symbol will not be versioned.

Probably introduced by commit

  ec6347bb4339 ("x86, powerpc: Rename memcpy_mcsafe() to copy_mc_to_{user, kernel}()")

-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2020-09-25  9:36 Stephen Rothwell
  0 siblings, 0 replies; 139+ messages in thread
From: Stephen Rothwell @ 2020-09-25  9:36 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: Linux Next Mailing List, Linux Kernel Mailing List


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

Hi all,

After merging the tip tree, today's linux-next build (powerpc and
powerpc64 allnoconfig) produced this warning:

WARNING: unmet direct dependencies detected for PCI_MSI_ARCH_FALLBACKS
  Depends on [n]: PCI [=n]
  Selected by [y]:
  - PPC [=y]

Introduced by commit

  077ee78e3928 ("PCI/MSI: Make arch_.*_msi_irq[s] fallbacks selectable")

-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2020-09-14  3:22 Stephen Rothwell
  2020-09-14 20:11 ` Kees Cook
  2020-10-03 21:54 ` Kees Cook
  0 siblings, 2 replies; 139+ messages in thread
From: Stephen Rothwell @ 2020-09-14  3:22 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: Kees Cook, Linux Next Mailing List, Linux Kernel Mailing List


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

Hi all,

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

x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_selftest_dynamic.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_kprobe_selftest.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_clock.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/ftrace.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/ring_buffer.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_output.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_seq.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_stat.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_printk.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/tracing_map.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_sched_switch.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_functions.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_preemptirq.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_irqsoff.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_sched_wakeup.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_hwlat.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_nop.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_stack.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_mmiotrace.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_functions_graph.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/blktrace.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/fgraph.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_events.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_export.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_syscalls.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_event_perf.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_events_filter.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_events_trigger.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_events_inject.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_events_synth.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_events_hist.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/bpf_trace.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_kprobe.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/power-traces.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/rpm-traces.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_kdb.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_dynevent.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_probe.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_uprobe.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_boot.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_benchmark.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_selftest_dynamic.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_kprobe_selftest.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_clock.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/ftrace.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/ring_buffer.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_output.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_seq.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_stat.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_printk.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/tracing_map.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_sched_switch.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_functions.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_preemptirq.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_irqsoff.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_sched_wakeup.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_hwlat.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_nop.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_stack.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_mmiotrace.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_functions_graph.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/blktrace.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/fgraph.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_events.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_export.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_syscalls.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_event_perf.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_events_filter.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_events_trigger.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_events_inject.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_events_synth.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_events_hist.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/bpf_trace.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_kprobe.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/power-traces.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/rpm-traces.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_kdb.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_dynevent.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_probe.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_uprobe.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_boot.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_benchmark.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_selftest_dynamic.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_kprobe_selftest.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_clock.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/ftrace.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/ring_buffer.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_output.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_seq.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_stat.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_printk.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/tracing_map.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_sched_switch.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_functions.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_preemptirq.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_irqsoff.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_sched_wakeup.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_hwlat.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_nop.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_stack.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_mmiotrace.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_functions_graph.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/blktrace.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/fgraph.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_events.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_export.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_syscalls.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_event_perf.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_events_filter.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_events_trigger.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_events_inject.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_events_synth.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_events_hist.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/bpf_trace.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_kprobe.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/power-traces.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/rpm-traces.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_kdb.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_dynevent.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_probe.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_uprobe.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_boot.o' being placed in section `.ctors.65435'
x86_64-linux-gnu-ld: warning: orphan section `.ctors.65435' from `kernel/trace/trace_benchmark.o' being placed in section `.ctors.65435'

Probably exposed by commit

  83109d5d5fba ("x86/build: Warn on orphan section placement")

-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2020-05-21 11:56 Stephen Rothwell
  0 siblings, 0 replies; 139+ messages in thread
From: Stephen Rothwell @ 2020-05-21 11:56 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: Linux Next Mailing List, Linux Kernel Mailing List


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

Hi all,

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

arch/x86/kernel/traps.c: In function 'exc_double_fault':
arch/x86/kernel/traps.c:332:16: warning: unused variable 'address' [-Wunused-variable]
  332 |  unsigned long address = read_cr2();
      |                ^~~~~~~

Introduced by commit

  095b7a3e7745 ("x86/entry: Convert double fault exception to IDTENTRY_DF")

-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2020-05-19  6:57 Stephen Rothwell
  2020-05-19  7:12 ` Steve French
  0 siblings, 1 reply; 139+ messages in thread
From: Stephen Rothwell @ 2020-05-19  6:57 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: Linux Next Mailing List, Linux Kernel Mailing List, Steve French, CIFS


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

Hi all,

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

fs/cifs/smb2inode.c: In function 'smb2_compound_op':
fs/cifs/smb2inode.c:424:1: warning: the frame size of 2736 bytes is larger than 2048 bytes [-Wframe-larger-than=]
  424 | }
      | ^

I have no idea what caused this.

-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2020-04-28  6:29 Stephen Rothwell
  0 siblings, 0 replies; 139+ messages in thread
From: Stephen Rothwell @ 2020-04-28  6:29 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: Linux Next Mailing List, Linux Kernel Mailing List, Josh Poimboeuf


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

Hi all,

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

arch/x86/kernel/unwind_orc.c:29:26: warning: 'cur_orc_table' defined but not used [-Wunused-variable]
   29 | static struct orc_entry *cur_orc_table = __start_orc_unwind;
      |                          ^~~~~~~~~~~~~
arch/x86/kernel/unwind_orc.c:28:13: warning: 'cur_orc_ip_table' defined but not used [-Wunused-variable]
   28 | static int *cur_orc_ip_table = __start_orc_unwind_ip;
      |             ^~~~~~~~~~~~~~~~

Exposed by commit

  153eb2223c79 ("x86/unwind/orc: Convert global variables to static")

This build has CONFIG_MODULE not set.

-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2020-01-20  5:38 Stephen Rothwell
  2020-01-20  6:00 ` Viresh Kumar
  0 siblings, 1 reply; 139+ messages in thread
From: Stephen Rothwell @ 2020-01-20  5:38 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: Linux Next Mailing List, Linux Kernel Mailing List, Viresh Kumar


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

Hi all,

After merging the tip tree, today's linux-next build (x86_64 allnoconfig
and a couple of other allnoconfigs) produced this warning:

kernel/sched/fair.c:5221:12: warning: 'sched_idle_cpu' defined but not used [-Wunused-function]
 5221 | static int sched_idle_cpu(int cpu)
      |            ^~~~~~~~~~~~~~

Introduced (I think) by commit

  323af6deaf70 ("sched/fair: Load balance aggressively for SCHED_IDLE CPUs")

-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2020-01-07  5:43 Stephen Rothwell
  2020-01-07  7:16 ` Ingo Molnar
  0 siblings, 1 reply; 139+ messages in thread
From: Stephen Rothwell @ 2020-01-07  5:43 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: Linux Next Mailing List, Linux Kernel Mailing List, Shile Zhang


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

Hi all,

[This has been happening for a while, I just missed it :-( ]

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

arch/x86/kernel/unwind_orc.c:210:12: warning: 'orc_sort_cmp' defined but not used [-Wunused-function]
  210 | static int orc_sort_cmp(const void *_a, const void *_b)
      |            ^~~~~~~~~~~~
arch/x86/kernel/unwind_orc.c:190:13: warning: 'orc_sort_swap' defined but not used [-Wunused-function]
  190 | static void orc_sort_swap(void *_a, void *_b, int size)
      |             ^~~~~~~~~~~~~

Introduced by commit

  f14bf6a350df ("x86/unwind/orc: Remove boot-time ORC unwind tables sorting")

-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2019-07-26  3:05 Stephen Rothwell
  2019-07-26  4:49 ` Josh Poimboeuf
  0 siblings, 1 reply; 139+ messages in thread
From: Stephen Rothwell @ 2019-07-26  3:05 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: Linux Next Mailing List, Linux Kernel Mailing List, Josh Poimboeuf


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

Hi all,

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

drivers/gpu/drm/i915/gem/i915_gem_execbuffer.o: warning: objtool: .altinstr_replacement+0x1c: redundant UACCESS disable

Presuambly introduced/uncovered by commit

  882a0db9d143 ("objtool: Improve UACCESS coverage")

-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2018-11-06  0:46 Stephen Rothwell
  2018-12-19  0:55 ` Stephen Rothwell
  0 siblings, 1 reply; 139+ messages in thread
From: Stephen Rothwell @ 2018-11-06  0:46 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: Linux-Next Mailing List, Linux Kernel Mailing List, Mark Rutland


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

Hi all,

After merging the tip tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:

warning: include/asm-generic/atomic-instrumented.h is out-of-date.
warning: include/asm-generic/atomic-long.h is out-of-date.
warning: include/linux/atomic-fallback.h is out-of-date.

Exposed by commit

  8d32588077bd ("locking/atomics: Check generated headers are up-to-date")

-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2018-09-11  3:53 Stephen Rothwell
  2018-09-12 19:35 ` Thomas Gleixner
  0 siblings, 1 reply; 139+ messages in thread
From: Stephen Rothwell @ 2018-09-11  3:53 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: Linux-Next Mailing List, Linux Kernel Mailing List, Andy Lutomirski


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

Hi all,

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

arch/x86/kernel/cpu/common.c: In function 'syscall_init':
arch/x86/kernel/cpu/common.c:1534:6: warning: unused variable 'cpu' [-Wunused-variable]
  int cpu = smp_processor_id();
      ^~~

Introduced by commit

  86635715ee42 ("x86/pti/64: Remove the SYSCALL64 entry trampoline")

-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2018-03-23  2:28 Stephen Rothwell
  2018-03-23  8:31 ` Christoph Hellwig
  0 siblings, 1 reply; 139+ messages in thread
From: Stephen Rothwell @ 2018-03-23  2:28 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: Linux-Next Mailing List, Linux Kernel Mailing List, Christoph Hellwig


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

Hi all,

After merging the tip tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:

lib/swiotlb.c:748:13: warning: 'swiotlb_free_buffer' defined but not used [-Wunused-function]
 static bool swiotlb_free_buffer(struct device *dev, size_t size,
             ^~~~~~~~~~~~~~~~~~~
lib/swiotlb.c:706:1: warning: 'swiotlb_alloc_buffer' defined but not used [-Wunused-function]
 swiotlb_alloc_buffer(struct device *dev, size_t size, dma_addr_t *dma_handle,
 ^~~~~~~~~~~~~~~~~~~~

Introduced by commit

  16e73adbca76 ("dma/swiotlb: Remove swiotlb_{alloc,free}_coherent()")

These are now only used with CONFIG_DMA_DIRECT_OPS.

-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2018-03-16  5:37 Stephen Rothwell
  2018-03-16  5:52 ` Dou Liyang
  2018-03-16  7:55 ` Thomas Gleixner
  0 siblings, 2 replies; 139+ messages in thread
From: Stephen Rothwell @ 2018-03-16  5:37 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: Linux-Next Mailing List, Linux Kernel Mailing List, Lai Jiangshan


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

Hi all,

After merging the tip tree, yesterday's linux-next build (x86_64 allnoconfig)
produced this warning:

kernel/cpu.c:129:13: warning: 'cpuhp_is_ap_state' defined but not used [-Wunused-function]
 static bool cpuhp_is_ap_state(enum cpuhp_state state)
             ^~~~~~~~~~~~~~~~~

Introduced by commit

  17a2f1ced028 ("cpu/hotplug: Merge cpuhp_bp_states and cpuhp_ap_states")

-- 
Cheers,
Stephen Rothwell

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

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2018-01-10  4:41 Stephen Rothwell
  0 siblings, 0 replies; 139+ messages in thread
From: Stephen Rothwell @ 2018-01-10  4:41 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: Linux-Next Mailing List, Linux Kernel Mailing List, David Woodhouse

Hi all,

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

arch/x86/kernel/cpu/bugs.c:79:12: warning: 'spectre_v2_enabled' defined but not used [-Wunused-variable]
 static int spectre_v2_enabled = SPECTRE_V2_NONE;
            ^

Introduced by commit

  54d5103245ff ("x86/spectre: Add boot time option to select Spectre v2 mitigation")

-- 
Cheers,
Stephen Rothwell

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2017-09-27  3:42 Stephen Rothwell
  2017-09-27 11:50 ` Prarit Bhargava
  0 siblings, 1 reply; 139+ messages in thread
From: Stephen Rothwell @ 2017-09-27  3:42 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: Linux-Next Mailing List, Linux Kernel Mailing List, Prarit Bhargava

Hi all,

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

kernel/printk/printk.c:1983:12: warning: 'printk_time' defined but not used [-Wunused-variable]
 static int printk_time;
            ^

Introduced by commit

  310b454a8653 ("printk: Add monotonic, boottime, and realtime timestamps")

-- 
Cheers,
Stephen Rothwell

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2017-06-28  7:15 Stephen Rothwell
  0 siblings, 0 replies; 139+ messages in thread
From: Stephen Rothwell @ 2017-06-28  7:15 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: Linux-Next Mailing List, Linux Kernel Mailing List, Rik van Riel

Hi all,

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

kernel/sched/fair.c:2657:9: warning: 'struct sched_domain' declared inside parameter list
         int prev_cpu, int sync)
         ^
/home/sfr/next/next/kernel/sched/fair.c:2657:9: warning: its scope is only this definition or declaration, which is probably not what you want

Introduced by commit

  3fed382b46ba ("sched/numa: Implement NUMA node level wake_affine()")

-- 
Cheers,
Stephen Rothwell

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2017-06-23  3:58 Stephen Rothwell
  2017-06-23  4:00 ` Stephen Rothwell
  0 siblings, 1 reply; 139+ messages in thread
From: Stephen Rothwell @ 2017-06-23  3:58 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: Linux-Next Mailing List, Linux Kernel Mailing List,
	Michael Ellerman, Benjamin Herrenschmidt, PowerPC

Hi all,

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

kernel/time/timekeeping.c:519:2: warning: #warning Please contact your maintainers, as GENERIC_TIME_VSYSCALL_OLD compatibity will disappear soon. [-Wcpp]
 #warning Please contact your maintainers, as GENERIC_TIME_VSYSCALL_OLD compatibity will disappear soon.
  ^
kernel/time/timekeeping.c:519:2: warning: #warning Please contact your maintainers, as GENERIC_TIME_VSYSCALL_OLD compatibity will disappear soon. [-Wcpp]
 #warning Please contact your maintainers, as GENERIC_TIME_VSYSCALL_OLD compatibity will disappear soon.
  ^

Introduced by commit

  369adf04d80a ("time: Add warning about imminent deprecation of CONFIG_GENERIC_TIME_VSYSCALL_OLD")

-- 
Cheers,
Stephen Rothwell

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2016-12-14  2:28 Stephen Rothwell
  2016-12-14  7:24 ` Ingo Molnar
  0 siblings, 1 reply; 139+ messages in thread
From: Stephen Rothwell @ 2016-12-14  2:28 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra,
	Artem Bityutskiy
  Cc: linux-next, linux-kernel, Richard Weinberger

Hi all,

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

fs/ubifs/dir.c: In function 'ubifs_readdir':
fs/ubifs/dir.c:629:13: warning: 'fstr_real_len' may be used uninitialized in this function [-Wmaybe-uninitialized]
    fstr.len = fstr_real_len;
             ^

Introduced by commit

  f4f61d2cc6d8 ("ubifs: Implement encrypted filenames")

This is a false positive because assignment and use are both protected by
"if (encrypted)".

I have no idea why this did not turn up earlier in my builds.

-- 
Cheers,
Stephen Rothwell

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2016-07-24  5:32 Stephen Rothwell
  2016-07-25  7:16 ` Thomas Gleixner
  0 siblings, 1 reply; 139+ messages in thread
From: Stephen Rothwell @ 2016-07-24  5:32 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra,
	Rich Felker
  Cc: linux-next, linux-kernel, Daniel Lezcano

Hi all,

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

In file included from include/linux/clocksource.h:18:0,
                 from include/linux/clockchips.h:13,
                 from drivers/clocksource/jcore-pit.c:14:
include/linux/of.h:1004:20: warning: comparison of distinct pointer types lacks a cast
        .data = (fn == (fn_type)NULL) ? fn : fn  }
                    ^
include/linux/of.h:1020:3: note: in expansion of macro '_OF_DECLARE'
   _OF_DECLARE(table, name, compat, fn, of_init_fn_1_ret)
   ^
include/linux/clocksource.h:247:2: note: in expansion of macro 'OF_DECLARE_1_RET'
  OF_DECLARE_1_RET(clksrc, name, compat, fn)
  ^
drivers/clocksource/jcore-pit.c:277:1: note: in expansion of macro 'CLOCKSOURCE_OF_DECLARE'
 CLOCKSOURCE_OF_DECLARE(jcore_pit, "jcore,pit", jcore_pit_init);
 ^

Introduced by commits

  b7c4db861683 ("clocksource/drivers/clksrc-probe: Introduce init functions with return code")
  177cf6e52b0a ("clocksources: Switch back to the clksrc table")

interacting with commit

  e0aa0655c60b ("clocksource: add J-Core timer/clocksource driver")

from the sh tree.

-- 
Cheers,
Stephen Rothwell

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2016-04-07  5:26 Stephen Rothwell
  2016-04-07  8:48 ` Ingo Molnar
  0 siblings, 1 reply; 139+ messages in thread
From: Stephen Rothwell @ 2016-04-07  5:26 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: linux-next, linux-kernel

Hi all,

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

mm/gup.c: In function 'get_user_pages_fast':
mm/gup.c:1510:20: warning: unused variable 'mm' [-Wunused-variable]
  struct mm_struct *mm = current->mm;
                    ^

Introduced by commit

  dc8cfd957d85 ("mm/gup: Remove the macro overload API migration helpers from the get_user*() APIs")

-- 
Cheers,
Stephen Rothwell

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2015-05-12  3:35 Stephen Rothwell
  0 siblings, 0 replies; 139+ messages in thread
From: Stephen Rothwell @ 2015-05-12  3:35 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: linux-next, linux-kernel


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

Hi all,

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

sound/drivers/pcsp/pcsp.c: In function 'snd_pcsp_create':
sound/drivers/pcsp/pcsp.c:51:5: warning: format '%li' expects argument of type 'long int', but argument 2 has type 'unsigned int' [-Wformat=]
     "(%linS)\n", resolution);
     ^

Introduced by commit 447fbbdc2cd5 ("sound: Use hrtimer_resolution
instead of hrtimer_get_res()").
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

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

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2014-08-05  0:58 Stephen Rothwell
  0 siblings, 0 replies; 139+ messages in thread
From: Stephen Rothwell @ 2014-08-05  0:58 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: linux-next, linux-kernel, NeilBrown


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

Hi all,

After merging the tip tree, the linux-next build (x86_64 allmodconfig)
for some time has produced this warning:

fs/cifs/misc.c:578:1: warning: 'cifs_oplock_break_wait' defined but not used [-Wunused-function]
 cifs_oplock_break_wait(void *unused)
 ^

Introduced by commit 743162013d40 ("sched: Remove proliferation of
wait_on_bit() action functions").  This commit is now in Linus' tree -
sorry for not noticing earlier.

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2014-07-18  5:00 Stephen Rothwell
  2014-07-18 19:16 ` H. Peter Anvin
  0 siblings, 1 reply; 139+ messages in thread
From: Stephen Rothwell @ 2014-07-18  5:00 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: linux-next, linux-kernel, Andy Lutomirski


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

Hi all,

After merging the tip tree, today's linux-next build (x86_64 allmodconfig)
produced these warnings:

In file included from arch/x86/vdso/vdso2c.c:161:0:
arch/x86/vdso/vdso2c.c: In function 'main':
arch/x86/vdso/vdso2c.h:118:6: warning: assuming signed overflow does not occur when assuming that (X + c) < X is always false [-Wstrict-overflow]
In file included from arch/x86/vdso/vdso2c.c:165:0:
arch/x86/vdso/vdso2c.h:118:6: warning: assuming signed overflow does not occur when assuming that (X + c) < X is always false [-Wstrict-overflow]

Probably introduced by commit e6577a7ce99a ("x86, vdso: Move the vvar
area before the vdso text").

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2014-06-16  1:57 Stephen Rothwell
  2014-06-20  4:24 ` Stephen Rothwell
  0 siblings, 1 reply; 139+ messages in thread
From: Stephen Rothwell @ 2014-06-16  1:57 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: linux-next, linux-kernel, Fenghua Yu


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

Hi all,

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

In file included from arch/x86/crypto/camellia_aesni_avx_glue.c:23:0:
arch/x86/include/asm/xsave.h:73:12: warning: 'xsave_state_booting' defined but not used [-Wunused-function]
 static int xsave_state_booting(struct xsave_struct *fx, u64 mask)
            ^

Lots of these ...

Introduced by commit adb9d526e982 ("x86/xsaves: Add xsaves and xrstors
support for booting time").  Forgotten "inline" :-(

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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2014-03-06  6:12 Stephen Rothwell
  0 siblings, 0 replies; 139+ messages in thread
From: Stephen Rothwell @ 2014-03-06  6:12 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: linux-next, linux-kernel, Stephane Eranian


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

Hi all,

After merging the tip tree, today's linux-next build (i386 defconfig)
produced this warning:

arch/x86/kernel/cpu/perf_event_intel_uncore.c: In function 'snb_uncore_imc_init_box':
arch/x86/kernel/cpu/perf_event_intel_uncore.c:1725:15: warning: unused variable 'addr_hi' [-Wunused-variable]

Introduced by commit b9e1ab6d4c05 ("perf/x86/uncore: add SNB/IVB/HSW
client uncore memory controller support") from the tip tree.
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

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

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2014-02-24  4:17 Stephen Rothwell
  2014-02-24  5:56 ` Stephen Rothwell
                   ` (2 more replies)
  0 siblings, 3 replies; 139+ messages in thread
From: Stephen Rothwell @ 2014-02-24  4:17 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: linux-next, linux-kernel, Andi Kleen


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

Hi all,

After merging the tip tree, today's linux-next build (arm
multi_v7_defconfig) produced this warning:

drivers/irqchip/irq-armada-370-xp.c:415:1: warning: 'externally_visible' attribute have effect only on public objects [-Wattributes]
drivers/irqchip/irq-sun4i.c:39:70: warning: 'externally_visible' attribute have effect only on public objects [-Wattributes]
drivers/irqchip/irq-sun4i.c:140:1: warning: 'externally_visible' attribute have effect only on public objects [-Wattributes]
drivers/irqchip/irq-gic.c:283:1: warning: 'externally_visible' attribute have effect only on public objects [-Wattributes]
drivers/irqchip/irq-sirfsoc.c:51:1: warning: 'externally_visible' attribute have effect only on public objects [-Wattributes]
drivers/irqchip/irq-vt8500.c:183:1: warning: 'externally_visible' attribute have effect only on public objects [-Wattributes]

Probably introduced by commit 128ea04a9885 ("lto: Make asmlinkage __visible").

I guess that there may be more places where "asmlinkage" is used with
"static" - I assume that they are all incorrect?

$ git grep -l 'static.*asmlinkage'
arch/x86/crypto/sha1_ssse3_glue.c
arch/x86/crypto/sha256_ssse3_glue.c
arch/x86/crypto/sha512_ssse3_glue.c
drivers/irqchip/irq-armada-370-xp.c
drivers/irqchip/irq-bcm2835.c
drivers/irqchip/irq-gic.c
drivers/irqchip/irq-mmp.c
drivers/irqchip/irq-moxart.c
drivers/irqchip/irq-orion.c
drivers/irqchip/irq-sirfsoc.c
drivers/irqchip/irq-sun4i.c
drivers/irqchip/irq-vic.c
drivers/irqchip/irq-vt8500.c
drivers/irqchip/irq-zevio.c
drivers/pnp/pnpbios/bioscalls.c
scripts/checkpatch.pl

(the last two don't matter)
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

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

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2013-08-19  4:26 Stephen Rothwell
  2013-08-19  6:58 ` Ingo Molnar
  0 siblings, 1 reply; 139+ messages in thread
From: Stephen Rothwell @ 2013-08-19  4:26 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: linux-next, linux-kernel, Andi Kleen


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

Hi all,

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

arch/x86/kernel/paravirt.c:66:0: warning: "DEF_NATIVE" redefined [enabled by default]
 #define DEF_NATIVE(ops, name, code)     \
 ^
In file included from arch/x86/include/asm/ptrace.h:65:0,
                 from arch/x86/include/asm/alternative.h:8,
                 from arch/x86/include/asm/bitops.h:16,
                 from include/linux/bitops.h:22,
                 from include/linux/kernel.h:10,
                 from include/linux/cache.h:4,
                 from include/linux/time.h:4,
                 from include/linux/stat.h:18,
                 from include/linux/module.h:10,
                 from arch/x86/kernel/paravirt.c:22:
arch/x86/include/asm/paravirt_types.h:391:0: note: this is the location of the previous definition
 #define DEF_NATIVE(ops, name, code)      \
 ^

Introduced by commit 9a55fdbe941e ("x86, asmlinkage, paravirt: Add
__visible/asmlinkage to xen paravirt ops").  The 2 definitions used to be
identical ... maybe there should be only one.

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

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

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2013-02-02  5:58 Stephen Rothwell
  0 siblings, 0 replies; 139+ messages in thread
From: Stephen Rothwell @ 2013-02-02  5:58 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: linux-next, linux-kernel, Dave Hansen


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

Hi all,

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

arch/x86/mm/numa.c: In function 'setup_node_data':
arch/x86/mm/numa.c:222:3: warning: passing argument 1 of '__phys_addr_nodebug' makes integer from pointer without a cast [enabled by default]
arch/x86/include/asm/page_64.h:12:29: note: expected 'long unsigned int' but argument is of type 'void *'

Introduced by commit a25b9316841c ("x86, mm: Make DEBUG_VIRTUAL work
earlier in boot").
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

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

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2013-02-02  5:55 Stephen Rothwell
  0 siblings, 0 replies; 139+ messages in thread
From: Stephen Rothwell @ 2013-02-02  5:55 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: linux-next, linux-kernel, Alok N Kataria


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

Hi all,

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

arch/x86/kernel/kvm.c: At top level:
arch/x86/kernel/kvm.c:509:2: warning: initialization from incompatible pointer type [enabled by default]
arch/x86/kernel/kvm.c:509:2: warning: (near initialization for 'x86_hyper_kvm.x2apic_available') [enabled by default]

Introduced by commit 4cca6ea04d31 ("x86/apic: Allow x2apic without IR on
VMware platform").
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

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

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2013-02-02  5:51 Stephen Rothwell
  0 siblings, 0 replies; 139+ messages in thread
From: Stephen Rothwell @ 2013-02-02  5:51 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: linux-next, linux-kernel, Dave Hansen


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

Hi all,

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

arch/x86/kernel/kvm.c: In function 'kvm_register_steal_time':
arch/x86/kernel/kvm.c:302:3: warning: format '%lx' expects argument of type 'long unsigned int', but argument 3 has type 'phys_addr_t' [-Wformat]

Introduced by commit 5dfd486c4750 ("x86, kvm: Fix kvm's use of __pa() on
percpu areas").

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

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

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2013-01-30 11:41 Stephen Rothwell
  0 siblings, 0 replies; 139+ messages in thread
From: Stephen Rothwell @ 2013-01-30 11:41 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: linux-next, linux-kernel, Dave Hansen


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

Hi all,

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

arch/x86/mm/numa.c: In function 'setup_node_data':
arch/x86/mm/numa.c:222:3: warning: passing argument 1 of '__phys_addr_nodebug' makes integer from pointer without a cast [enabled by default]
arch/x86/include/asm/page_64.h:12:29: note: expected 'long unsigned int' but argument is of type 'void *'

Introduced by commit a25b9316841c ("x86, mm: Make DEBUG_VIRTUAL work
earlier in boot").
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

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

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2012-10-01 14:54 Stephen Rothwell
  2012-10-01 16:10 ` Josh Triplett
  0 siblings, 1 reply; 139+ messages in thread
From: Stephen Rothwell @ 2012-10-01 14:54 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: linux-next, linux-kernel, Josh Triplett


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

Hi all,

After merging the tip tree, today's linux-next build (sparc64 defconfig)
produced this warning:

include/linux/efi.h:503:13: warning: 'efi_enter_virtual_mode' defined but not used [-Wunused-function]
include/linux/efi.h:504:13: warning: 'efi_late_init' defined but not used [-Wunused-function]
include/linux/efi.h:505:13: warning: 'efi_free_boot_services' defined but not used [-Wunused-function]

Introduced by commit f383a1e37bc3 ("efi: Add a stub for
efi_enter_virtual_mode on non-x86") and following patches.  These
function definitions should be "static inline".
-- 
Cheers,
Stephen Rothwell                    sfr@canb.auug.org.au

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

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2012-09-27  7:46 Stephen Rothwell
  0 siblings, 0 replies; 139+ messages in thread
From: Stephen Rothwell @ 2012-09-27  7:46 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: linux-next, linux-kernel


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

Hi all,

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

mm/memory.c: In function 'do_prot_none':
mm/memory.c:3463:6: warning: unused variable 'node' [-Wunused-variable]

Introduced by commit 39d6cb39a817 ("mm/mpol: Use special PROT_NONE to
migrate pages").

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

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

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2011-09-14  6:34 Stephen Rothwell
  2011-09-14  7:49 ` Yong Zhang
  2011-09-14  9:37 ` Thomas Gleixner
  0 siblings, 2 replies; 139+ messages in thread
From: Stephen Rothwell @ 2011-09-14  6:34 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: linux-next, linux-kernel, Shan Hai, Yong Zhang


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

Hi all,

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

lib/atomic64.c: In function 'lock_addr':
lib/atomic64.c:42:2: warning: return from incompatible pointer type

Introduced by commit f59ca05871a0 ("locking, lib/atomic64: Annotate
atomic64_lock::lock as raw").  This function (which is declared to return
"spinlock_t *") is now returning "raw_spinlock_t *".
-- 
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] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2011-09-14  6:22 Stephen Rothwell
  0 siblings, 0 replies; 139+ messages in thread
From: Stephen Rothwell @ 2011-09-14  6:22 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: linux-next, linux-kernel, John Stultz


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

Hi all,

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

kernel/time/alarmtimer.c: In function 'alarmtimer_rtc_interface_setup':
kernel/time/alarmtimer.c:106:26: warning: ignoring return value of 'class_interface_register', declared with attribute warn_unused_result

Introduced by commit 8bc0dafb5cf3 ("alarmtimers: Rework RTC device
selection using class interface").

-- 
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] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2010-11-29  1:11 Stephen Rothwell
  0 siblings, 0 replies; 139+ messages in thread
From: Stephen Rothwell @ 2010-11-29  1:11 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: linux-next, linux-kernel


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

Hi all,

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

kernel/sched.c: In function 'sched_destroy_group':
kernel/sched.c:8098: warning: 'i' is used uninitialized in this function
kernel/sched.c:8088: note: 'i' was declared here

Introduced by commit 3d4b47b4b040c9d77dd68104cfc1055d89a55afd ("sched:
Implement on-demand (active) cfs_rq list").  I think this is a real bug.

[The wrong function is mentioned above, the actual function is
unregister_fair_sched_group() - presumably gcc has confused itself via
inlining.]
-- 
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] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2010-09-03  2:10 Stephen Rothwell
  2010-09-03  2:12 ` Stephen Rothwell
  0 siblings, 1 reply; 139+ messages in thread
From: Stephen Rothwell @ 2010-09-03  2:10 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: linux-next, linux-kernel, Haicheng Li, Andi Kleen, Wu Fengguang


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

Hi all,

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

arch/x86/mm/init_64.c: In function 'kernel_physical_mapping_init':
arch/x86/mm/init_64.c:601: warning: 'addr' may be used uninitialized in this function

The code does look suspicious ... 'addr' gets declared and then passed to
a function, but is not set anywhere ...

-- 
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] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2010-05-17  5:58 Stephen Rothwell
  0 siblings, 0 replies; 139+ messages in thread
From: Stephen Rothwell @ 2010-05-17  5:58 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: linux-next, linux-kernel, Tony Breeds, Benjamin Herrenschmidt


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

Hi all,

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

kernel/mutex.c: In function '__mutex_lock_common':
kernel/mutex.c:148: warning: unused variable 'timeout'

Introduced by commit 227945799cc10d77c6ef812f3eb8a61a78689454 ("mutex:
Fix optimistic spinning vs. BKL") for a build with
CONFIG_MUTEX_SPIN_ON_OWNER not set.

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

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

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2010-03-17  3:57 Stephen Rothwell
  2010-03-17  4:00 ` KOSAKI Motohiro
  2010-03-17  7:02 ` Ingo Molnar
  0 siblings, 2 replies; 139+ messages in thread
From: Stephen Rothwell @ 2010-03-17  3:57 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: linux-next, linux-kernel, KOSAKI Motohiro


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

Hi all,

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

kernel/sched.c: In function 'SYSC_sched_getaffinity':
kernel/sched.c:4915: warning: comparison of distinct pointer types lacks a cast

Introduced by commit cd3d8031eb4311e516329aee03c79a08333141f1 ("sched:
sched_getaffinity(): Allow less than NR_CPUS length").  Just a usage of
min() with different types.

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

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

^ permalink raw reply	[flat|nested] 139+ messages in thread
* linux-next: build warning after merge of the tip tree
@ 2010-02-23  5:01 Stephen Rothwell
  2010-02-23  8:52 ` Yinghai Lu
  0 siblings, 1 reply; 139+ messages in thread
From: Stephen Rothwell @ 2010-02-23  5:01 UTC (permalink / raw)
  To: Thomas Gleixner, Ingo Molnar, H. Peter Anvin, Peter Zijlstra
  Cc: linux-next, linux-kernel, Yinghai Lu


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

Hi all,

After merging the tip tree, today's linux-next build (powerpc
ppc64_defconfig) produced these warnings:

mm/sparse.c: In function 'sparse_init':
mm/sparse.c:488: warning: unused variable 'map_count'
mm/sparse.c:484: warning: unused variable 'size2'
mm/sparse.c:481: warning: unused variable 'map_map'
mm/sparse.c: At top level:
mm/sparse.c:442: warning: 'sparse_early_mem_maps_alloc_node' defined but not used

Introduced by commit 9bdac914240759457175ac0d6529a37d2820bc4d
("sparsemem: Put mem map for one node together").

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

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

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

end of thread, back to index

Thread overview: 139+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-03-30  2:47 linux-next: build warning after merge of the tip tree Stephen Rothwell
2020-03-31 21:57 ` Stephen Rothwell
2020-04-01 10:25   ` Thomas Gleixner
2020-04-01 22:00     ` Stephen Rothwell
2020-04-01 22:39       ` Thomas Gleixner
2020-04-13  0:01         ` Stephen Rothwell
2020-04-14  8:42           ` Thomas Gleixner
2020-04-14  9:07           ` ARM: futex: Address build warning Thomas Gleixner
2020-05-06 22:19             ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2020-11-05  7:06 linux-next: build warning after merge of the tip tree Stephen Rothwell
2020-11-06  4:35 ` Stephen Rothwell
2020-10-28  3:23 Stephen Rothwell
2020-11-15 22:17 ` Stephen Rothwell
2020-11-15 22:23 ` Balbir Singh
2020-11-17  5:21   ` Balbir Singh
2020-11-23  7:23     ` Stephen Rothwell
2020-10-08  4:28 Stephen Rothwell
2020-10-08  9:02 ` Borislav Petkov
2020-09-25  9:36 Stephen Rothwell
2020-09-14  3:22 Stephen Rothwell
2020-09-14 20:11 ` Kees Cook
2020-09-14 22:35   ` Stephen Rothwell
2020-10-01 11:02     ` Stephen Rothwell
2020-10-02 22:46       ` Kees Cook
2020-10-03 21:54 ` Kees Cook
2020-10-03 23:24   ` Stephen Rothwell
2020-10-04  7:42     ` Kees Cook
2020-10-04  8:27     ` Kees Cook
2020-10-04 10:00       ` Stephen Rothwell
2020-10-05  2:44         ` Kees Cook
2020-10-14 22:25           ` Stephen Rothwell
2020-10-14 23:10             ` Kees Cook
2020-10-15  0:19               ` Stephen Rothwell
2020-05-21 11:56 Stephen Rothwell
2020-05-19  6:57 Stephen Rothwell
2020-05-19  7:12 ` Steve French
2020-04-28  6:29 Stephen Rothwell
2020-01-20  5:38 Stephen Rothwell
2020-01-20  6:00 ` Viresh Kumar
2020-01-07  5:43 Stephen Rothwell
2020-01-07  7:16 ` Ingo Molnar
2020-01-07  7:22   ` Shile Zhang
2019-07-26  3:05 Stephen Rothwell
2019-07-26  4:49 ` Josh Poimboeuf
2019-07-26  5:49   ` Stephen Rothwell
2018-11-06  0:46 Stephen Rothwell
2018-12-19  0:55 ` Stephen Rothwell
2018-09-11  3:53 Stephen Rothwell
2018-09-12 19:35 ` Thomas Gleixner
2018-03-23  2:28 Stephen Rothwell
2018-03-23  8:31 ` Christoph Hellwig
2018-03-23  9:57   ` Stephen Rothwell
2018-03-16  5:37 Stephen Rothwell
2018-03-16  5:52 ` Dou Liyang
2018-03-16  6:04   ` Dou Liyang
2018-03-16  7:55 ` Thomas Gleixner
2018-01-10  4:41 Stephen Rothwell
2017-09-27  3:42 Stephen Rothwell
2017-09-27 11:50 ` Prarit Bhargava
2017-06-28  7:15 Stephen Rothwell
2017-06-23  3:58 Stephen Rothwell
2017-06-23  4:00 ` Stephen Rothwell
2017-06-23  4:10   ` Michael Ellerman
2017-06-23  4:22     ` Stephen Rothwell
2016-12-14  2:28 Stephen Rothwell
2016-12-14  7:24 ` Ingo Molnar
2016-12-14  8:05   ` Richard Weinberger
2016-12-14  8:26     ` Stephen Rothwell
2016-12-14  8:10   ` Stephen Rothwell
2016-07-24  5:32 Stephen Rothwell
2016-07-25  7:16 ` Thomas Gleixner
2016-07-25 13:11   ` Daniel Lezcano
2016-07-25 14:53     ` Rich Felker
2016-07-25 16:42       ` Mark Brown
2016-07-25 17:54         ` Rich Felker
2016-07-25 14:48   ` Rich Felker
2016-04-07  5:26 Stephen Rothwell
2016-04-07  8:48 ` Ingo Molnar
2016-04-07 12:03   ` Stephen Rothwell
2015-05-12  3:35 Stephen Rothwell
2014-08-05  0:58 Stephen Rothwell
2014-07-18  5:00 Stephen Rothwell
2014-07-18 19:16 ` H. Peter Anvin
2014-07-18 19:57   ` Andy Lutomirski
2014-07-18 20:05     ` H. Peter Anvin
2014-07-18 20:08       ` Andy Lutomirski
2014-07-18 20:15         ` H. Peter Anvin
2014-07-18 20:20           ` Andy Lutomirski
2014-07-18 20:50             ` H. Peter Anvin
2014-06-16  1:57 Stephen Rothwell
2014-06-20  4:24 ` Stephen Rothwell
2014-06-20  4:30   ` H. Peter Anvin
2014-06-20  4:35     ` Stephen Rothwell
2014-03-06  6:12 Stephen Rothwell
2014-02-24  4:17 Stephen Rothwell
2014-02-24  5:56 ` Stephen Rothwell
2014-02-24  6:12   ` Andrew Morton
2014-02-24  6:23     ` Stephen Rothwell
2014-02-24 15:48 ` Andi Kleen
2014-02-24 15:51   ` H. Peter Anvin
2014-03-06  4:00 ` Stephen Rothwell
2014-03-28  5:52   ` Stephen Rothwell
2014-03-31  9:45     ` Thomas Gleixner
2014-03-31 10:57       ` Stephen Rothwell
2014-04-01  0:26         ` Stephen Rothwell
2014-04-01  1:56           ` H. Peter Anvin
2013-08-19  4:26 Stephen Rothwell
2013-08-19  6:58 ` Ingo Molnar
2013-08-20  0:52   ` Andi Kleen
2013-08-20  6:42     ` Ingo Molnar
2013-08-30  8:55       ` Stephen Rothwell
2013-08-30 20:42         ` Andi Kleen
2013-08-31  6:41           ` Ingo Molnar
2013-02-02  5:58 Stephen Rothwell
2013-02-02  5:55 Stephen Rothwell
2013-02-02  5:51 Stephen Rothwell
2013-01-30 11:41 Stephen Rothwell
2012-10-01 14:54 Stephen Rothwell
2012-10-01 16:10 ` Josh Triplett
2012-09-27  7:46 Stephen Rothwell
2011-09-14  6:34 Stephen Rothwell
2011-09-14  7:49 ` Yong Zhang
2011-09-14  9:37 ` Thomas Gleixner
2011-09-14  9:43   ` Shan Hai
2011-09-14  6:22 Stephen Rothwell
2010-11-29  1:11 Stephen Rothwell
2010-09-03  2:10 Stephen Rothwell
2010-09-03  2:12 ` Stephen Rothwell
2010-09-03  9:04   ` Wu Fengguang
2010-09-03 10:07     ` Haicheng Li
2010-05-17  5:58 Stephen Rothwell
2010-03-17  3:57 Stephen Rothwell
2010-03-17  4:00 ` KOSAKI Motohiro
2010-03-17  4:52   ` Stephen Rothwell
2010-03-17  7:02 ` Ingo Molnar
2010-03-17  8:02   ` KOSAKI Motohiro
2010-02-23  5:01 Stephen Rothwell
2010-02-23  8:52 ` Yinghai Lu
2010-02-23 10:43   ` 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