From: Zong Li <zong.li@sifive.com>
To: palmer@dabbelt.com, paul.walmsley@sifive.com,
linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: Zong Li <zong.li@sifive.com>
Subject: [PATCH v2 0/2] Fix some build warnings when W=1
Date: Thu, 16 Jul 2020 21:05:44 +0800 [thread overview]
Message-ID: <cover.1594886530.git.zong.li@sifive.com> (raw)
These patches fix some build warnings when W=1, the most of warnings are
missing prototype as follows:
arch/riscv/mm/init.c:520:13: warning: no previous prototype for 'resource_init' [-Wmissing-prototypes]
arch/riscv/mm/pageattr.c:130:5: warning: no previous prototype for 'set_memory_ro' [-Wmissing-prototypes]
arch/riscv/mm/pageattr.c:136:5: warning: no previous prototype for 'set_memory_rw' [-Wmissing-prototypes]
arch/riscv/mm/pageattr.c:142:5: warning: no previous prototype for 'set_memory_x' [-Wmissing-prototypes]
arch/riscv/mm/pageattr.c:147:5: warning: no previous prototype for 'set_memory_nx' [-Wmissing-prototypes]
arch/riscv/mm/pageattr.c:152:5: warning: no previous prototype for 'set_direct_map_invalid_noflush' [-Wmissing-prototypes]
arch/riscv/mm/pageattr.c:169:5: warning: no previous prototype for 'set_direct_map_default_noflush' [-Wmissing-prototypes]
arch/riscv/mm/pageattr.c:97:1: warning: 'static' is not at beginning of declaration [-Wold-style-declaration]
Changed in v2:
- Modify the patch description
Zong Li (2):
riscv: Fix build warning for mm/init
riscv: Fix build warning for mm/pageattr
arch/riscv/mm/init.c | 2 +-
arch/riscv/mm/pageattr.c | 3 ++-
2 files changed, 3 insertions(+), 2 deletions(-)
--
2.27.0
next reply other threads:[~2020-07-16 13:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-16 13:05 Zong Li [this message]
2020-07-16 13:05 ` [PATCH v2 1/2] riscv: Fix build warning for mm/init Zong Li
2020-07-16 13:07 ` Pekka Enberg
2020-07-16 13:19 ` Anup Patel
2020-07-16 13:05 ` [PATCH v2 2/2] riscv: Fix build warning for mm/pageattr Zong Li
2020-07-16 13:20 ` Anup Patel
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=cover.1594886530.git.zong.li@sifive.com \
--to=zong.li@sifive.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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