From: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
To: Wujie Duan <wjduan@linx-info.com>
Cc: linux-mips@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Mark symbols static where possible for mips/kernel
Date: Tue, 28 Nov 2023 10:00:24 +0100 [thread overview]
Message-ID: <ZWWsKBmjMKYZtWpu@alpha.franken.de> (raw)
In-Reply-To: <20231128071225.801111-1-wjduan@linx-info.com>
On Tue, Nov 28, 2023 at 03:12:25PM +0800, Wujie Duan wrote:
> We get 1 error when building kernel with -Werror=missing-prototypes
check git grep setup_sigcontext arch/mips/
With this patch n32 support doesn't build. We need a prototype in a header
to fix that.
Thomas.
--
Crap can work. Given enough thrust pigs will fly, but it's not necessarily a
good idea. [ RFC1925, 2.3 ]
next prev parent reply other threads:[~2023-11-28 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-28 7:12 [PATCH] Mark symbols static where possible for mips/kernel Wujie Duan
2023-11-28 9:00 ` Thomas Bogendoerfer [this message]
2023-11-28 22:51 ` kernel test robot
2023-11-30 11:00 ` kernel test robot
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=ZWWsKBmjMKYZtWpu@alpha.franken.de \
--to=tsbogend@alpha.franken.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mips@vger.kernel.org \
--cc=wjduan@linx-info.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