From: Will Deacon <will@kernel.org>
To: samitolvanen@google.com, amit.kachhap@arm.com,
keescook@chromium.org, mark.rutland@arm.com,
0x7f454c46@gmail.com, Maninder Singh <maninder1.s@samsung.com>,
catalin.marinas@arm.com, akpm@linux-foundation.org,
pcc@google.com, james.morse@arm.com, vincenzo.frascino@arm.com,
nsaenzjulienne@suse.de
Cc: kernel-team@android.com, Will Deacon <will@kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, a.sahrawat@samsung.com
Subject: Re: (subset) [PATCH 1/2] arm64/process.c: fix Wmissing-prototypes build warnings
Date: Thu, 25 Mar 2021 11:19:03 +0000 [thread overview]
Message-ID: <161666581740.223087.673529524234867266.b4-ty@kernel.org> (raw)
In-Reply-To: <1616568899-986-1-git-send-email-maninder1.s@samsung.com>
On Wed, 24 Mar 2021 12:24:58 +0530, Maninder Singh wrote:
> function protypes are missed before defination, which
> leads to compilation warning with "-Wmissing-prototypes"
> flag.
>
> https://lkml.org/lkml/2021/3/19/840
>
> arch/arm64/kernel/process.c:261:6: warning: no previous prototype for '__show_regs' [-Wmissing-prototypes]
> 261 | void __show_regs(struct pt_regs *regs)
> | ^~~~~~~~~~~
> arch/arm64/kernel/process.c:307:6: warning: no previous prototype for '__show_regs_alloc_free' [-Wmissing-prototypes]
> 307 | void __show_regs_alloc_free(struct pt_regs *regs)
> | ^~~~~~~~~~~~~~~~~~~~~~
> arch/arm64/kernel/process.c:365:5: warning: no previous prototype for 'arch_dup_task_struct' [-Wmissing-prototypes]
> 365 | int arch_dup_task_struct(struct task_struct *dst, struct task_struct *src)
> | ^~~~~~~~~~~~~~~~~~~~
> arch/arm64/kernel/process.c:546:41: warning: no previous prototype for '__switch_to' [-Wmissing-prototypes]
> 546 | __notrace_funcgraph struct task_struct *__switch_to(struct task_struct *prev,
> | ^~~~~~~~~~~
> arch/arm64/kernel/process.c:710:25: warning: no previous prototype for 'arm64_preempt_schedule_irq' [-Wmissing-prototypes]
> 710 | asmlinkage void __sched arm64_preempt_schedule_irq(void)
> | ^~~~~~~~~~~~~~~~~~~~~~~~~~
Applied first patch ONLY to arm64 (for-next/fixes), thanks!
[1/2] arm64/process.c: fix Wmissing-prototypes build warnings
https://git.kernel.org/arm64/c/baa96377bc7b
Cheers,
--
Will
https://fixes.arm64.dev
https://next.arm64.dev
https://will.arm64.dev
prev parent reply other threads:[~2021-03-25 11:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20210324065511epcas5p1cb74119660e2d98a381ae69d01b29275@epcas5p1.samsung.com>
2021-03-24 6:54 ` [PATCH 1/2] arm64/process.c: fix Wmissing-prototypes build warnings Maninder Singh
[not found] ` <CGME20210324065516epcas5p450958011b69f5941e8f2bc993b82b904@epcas5p4.samsung.com>
2021-03-24 6:54 ` [PATCH 2/2] arm64: print alloc free paths for address in registers Maninder Singh
2021-03-24 11:51 ` Mark Rutland
[not found] ` <CGME20210324065516epcas5p450958011b69f5941e8f2bc993b82b904@epcms5p3>
2021-03-24 14:40 ` Maninder Singh
2021-03-25 11:19 ` Will Deacon [this message]
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=161666581740.223087.673529524234867266.b4-ty@kernel.org \
--to=will@kernel.org \
--cc=0x7f454c46@gmail.com \
--cc=a.sahrawat@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=amit.kachhap@arm.com \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=keescook@chromium.org \
--cc=kernel-team@android.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maninder1.s@samsung.com \
--cc=mark.rutland@arm.com \
--cc=nsaenzjulienne@suse.de \
--cc=pcc@google.com \
--cc=samitolvanen@google.com \
--cc=vincenzo.frascino@arm.com \
/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).