From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Jinyang He <hejinyang@loongson.cn>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] MIPS: process: Fix no previous prototype warning
Date: Tue, 9 Feb 2021 13:37:46 +0100 [thread overview]
Message-ID: <20210209123746.GD11264@alpha.franken.de> (raw)
In-Reply-To: <1612687956-28075-1-git-send-email-hejinyang@loongson.cn>
On Sun, Feb 07, 2021 at 04:52:36PM +0800, Jinyang He wrote:
> unwind_stack_by_address and unwind_stack need <asm/stacktrace.h>.
> arch_align_stack needs <asm/exec.h>
>
> link: https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org/thread/ZPL2RRA6RZKRQZI5IGOVLFXN2GVZBN3L/
> Fixes: ("MIPS: process: Remove unnecessary headers inclusion")
this Fixes is broken, it's missing a git hash. But there is no reason
for a fixes tag, because it "only" removed a warning, but doesn't fix
a bug. So I've removed it while applying the patch.
> Reported-by: kernel test robot <lkp@intel.com>
> Signed-off-by: Jinyang He <hejinyang@loongson.cn>
> ---
> arch/mips/kernel/process.c | 2 ++
> 1 file changed, 2 insertions(+)
applied to mips-next.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
prev parent reply other threads:[~2021-02-09 12:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-07 8:52 [PATCH] MIPS: process: Fix no previous prototype warning Jinyang He
2021-02-09 12:37 ` Thomas Bogendoerfer [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=20210209123746.GD11264@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=hejinyang@loongson.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.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).