public inbox for linux-next@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux Next Mailing List <linux-next@vger.kernel.org>
Subject: linux-next: build warnings after merge of the origin tree
Date: Tue, 30 Jul 2024 08:22:04 +1000	[thread overview]
Message-ID: <20240730082204.57c64765@canb.auug.org.au> (raw)

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

Hi all,

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

In file included from include/asm-generic/percpu.h:7,
                 from arch/powerpc/include/asm/percpu.h:28,
                 from include/linux/irqflags.h:19,
                 from include/linux/spinlock.h:59,
                 from include/linux/mmzone.h:8,
                 from include/linux/gfp.h:7,
                 from include/linux/mm.h:7,
                 from include/linux/memblock.h:12,
                 from kernel/profile.c:20:
kernel/profile.c:52:28: warning: 'cpu_profile_flip' defined but not used [-Wunused-variable]
   52 | static DEFINE_PER_CPU(int, cpu_profile_flip);
      |                            ^~~~~~~~~~~~~~~~
include/linux/percpu-defs.h:104:44: note: in definition of macro 'DEFINE_PER_CPU_SECTION'
  104 |         __PCPU_ATTRS(sec) __typeof__(type) name
      |                                            ^~~~
kernel/profile.c:52:8: note: in expansion of macro 'DEFINE_PER_CPU'
   52 | static DEFINE_PER_CPU(int, cpu_profile_flip);
      |        ^~~~~~~~~~~~~~
kernel/profile.c:51:48: warning: 'cpu_profile_hits' defined but not used [-Wunused-variable]
   51 | static DEFINE_PER_CPU(struct profile_hit *[2], cpu_profile_hits);
      |                                                ^~~~~~~~~~~~~~~~
include/linux/percpu-defs.h:104:44: note: in definition of macro 'DEFINE_PER_CPU_SECTION'
  104 |         __PCPU_ATTRS(sec) __typeof__(type) name
      |                                            ^~~~
kernel/profile.c:51:8: note: in expansion of macro 'DEFINE_PER_CPU'
   51 | static DEFINE_PER_CPU(struct profile_hit *[2], cpu_profile_hits);
      |        ^~~~~~~~~~~~~~

Introduced by commit

  2accfdb7eff6 ("profiling: attempt to remove per-cpu profile flip buffer")

-- 
Cheers,
Stephen Rothwell

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

             reply	other threads:[~2024-07-29 22:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-29 22:22 Stephen Rothwell [this message]
2024-07-29 23:38 ` linux-next: build warnings after merge of the origin tree Linus Torvalds
2024-07-29 23:57   ` Linus Torvalds
2024-07-30  5:22 ` Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2023-05-08  4:39 Stephen Rothwell
2023-05-08  6:31 ` Maher Sanalla
2022-06-20  8:02 Stephen Rothwell
2021-02-18 21:02 Stephen Rothwell
2021-02-19 15:33 ` Vitaly Kuznetsov
2021-02-19 16:01   ` Paolo Bonzini
2021-02-23 21:56     ` Stephen Rothwell
2021-02-26  1:57       ` Stephen Rothwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20240730082204.57c64765@canb.auug.org.au \
    --to=sfr@canb.auug.org.au \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox