linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Thiago Jung Bauermann <bauerman@linux.vnet.ibm.com>
Cc: Arnd Bergmann <arnd@arndb.de>,
	linux-kernel@vger.kernel.org, Paul Mackerras <paulus@samba.org>,
	Miguel Ojeda <ojeda@kernel.org>,
	linuxppc-dev@lists.ozlabs.org,
	Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Subject: ppc64_defconfig Werror: no previous prototype on arch/powerpc/kernel/ftrace.c
Date: Wed, 27 Apr 2022 13:26:25 +0700	[thread overview]
Message-ID: <YmjiEUxHaQ6OQV30@debian.me> (raw)

Greetings,

I did ppc64_defconfig build (gcc 11.2.0) on current master at commit
46cf2c613f4b10 ("Merge tag 'pinctrl-v5.18-2'
of git://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl"),
and it errored out early like this:

  CC      arch/powerpc/kernel/trace/ftrace.o
arch/powerpc/kernel/trace/ftrace.c:978:7: error: no previous prototype for ‘arch_ftrace_match_adjust’ [-Werror=missing-prototypes]
  978 | char *arch_ftrace_match_adjust(char *str, const char *search)
      |       ^~~~~~~~~~~~~~~~~~~~~~~~
  CC      init/init_task.o
cc1: all warnings being treated as errors
make[3]: *** [scripts/Makefile.build:288: arch/powerpc/kernel/trace/ftrace.o] Error 1
make[2]: *** [scripts/Makefile.build:550: arch/powerpc/kernel/trace] Error 2
make[1]: *** [scripts/Makefile.build:550: arch/powerpc/kernel] Error 2
make: *** [Makefile:1834: arch/powerpc] Error 2

The code in question is introduced by commit 7132e2d669bd42 ("ftrace:
Match dot symbols when searching functions on ppc64").

Reported-by: Bagas Sanjaya <bagasdotme@gmail.com>

-- 
An old man doll... just what I always wanted! - Clara

                 reply	other threads:[~2022-04-27  6:27 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=YmjiEUxHaQ6OQV30@debian.me \
    --to=bagasdotme@gmail.com \
    --cc=arnd@arndb.de \
    --cc=bauerman@linux.vnet.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=luc.vanoostenryck@gmail.com \
    --cc=ojeda@kernel.org \
    --cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).