From: Nathan Chancellor <nathan@kernel.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Brian Cain <bcain@codeaurora.org>,
Yoshinori Sato <ysato@users.sourceforge.jp>,
Guo Ren <guoren@kernel.org>,
linux-kernel@vger.kernel.org,
Nathan Chancellor <nathan@kernel.org>
Subject: [PATCH 1/3] hexagon: Fix function name in die()
Date: Mon, 27 Dec 2021 11:48:49 -0700 [thread overview]
Message-ID: <20211227184851.2297759-2-nathan@kernel.org> (raw)
In-Reply-To: <20211227184851.2297759-1-nathan@kernel.org>
When building ARCH=hexagon defconfig:
arch/hexagon/kernel/traps.c:217:2: error: implicit declaration of
function 'make_dead_task' [-Werror,-Wimplicit-function-declaration]
make_dead_task(err);
^
The function's name is make_task_dead(), change it so there is no more
build error.
Fixes: 0e25498f8cd4 ("exit: Add and use make_task_dead.")
Signed-off-by: Nathan Chancellor <nathan@kernel.org>
---
arch/hexagon/kernel/traps.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/hexagon/kernel/traps.c b/arch/hexagon/kernel/traps.c
index 6dd6cf0ab711..1240f038cce0 100644
--- a/arch/hexagon/kernel/traps.c
+++ b/arch/hexagon/kernel/traps.c
@@ -214,7 +214,7 @@ int die(const char *str, struct pt_regs *regs, long err)
panic("Fatal exception");
oops_exit();
- make_dead_task(err);
+ make_task_dead(err);
return 0;
}
--
2.34.1
next prev parent reply other threads:[~2021-12-27 18:51 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-27 18:48 [PATCH 0/3] Fix build errors with do_exit() to make_task_dead() transition Nathan Chancellor
2021-12-27 18:48 ` Nathan Chancellor [this message]
2021-12-27 18:48 ` [PATCH 2/3] h8300: Fix build errors from " Nathan Chancellor
2021-12-27 18:48 ` [PATCH 3/3] csky: Fix function name in csky_alignment() and die() Nathan Chancellor
2021-12-28 1:46 ` Guo Ren
2021-12-28 1:47 ` Guo Ren
2021-12-28 1:53 ` Guo Ren
2021-12-28 2:01 ` Guo Ren
2021-12-28 2:18 ` Nathan Chancellor
2021-12-28 2:50 ` Guo Ren
2021-12-29 16:29 ` Eric W. Biederman
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=20211227184851.2297759-2-nathan@kernel.org \
--to=nathan@kernel.org \
--cc=bcain@codeaurora.org \
--cc=ebiederm@xmission.com \
--cc=guoren@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ysato@users.sourceforge.jp \
/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