From: Stafford Horne <shorne@gmail.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: Stafford Horne <shorne@gmail.com>
Subject: [PATCH 0/6] OpenRISC header and sparse warning fixes for 5.9
Date: Tue, 4 Aug 2020 13:23:48 +0900 [thread overview]
Message-ID: <20200804042354.3930694-1-shorne@gmail.com> (raw)
Hello,
This a series of fixes for OpenRISC sparse warnings. The kbuild robots report
many issues related to issues with OpenRISC headers having missing or incorrect
sparse annotations.
Example kdbuild-all report:
net/ipv4/ip_sockglue.c:1489:13: sparse: sparse: incorrect type in initializer (different address spaces)
https://lists.01.org/hyperkitty/list/kbuild-all@lists.01.org/thread/MB6SE7BX425ENFTSIL6KAOB3CVS4WJLH/
Also this includes a few cleanups which I noticed while working on the warning
fixups.
-Stafford
Stafford Horne (6):
openrisc: io: Fixup defines and move include to the end
openrisc: uaccess: Fix sparse address space warnings
openrisc: uaccess: Use static inline function in access_ok
openrisc: uaccess: Remove unused macro __addr_ok
openrisc: signal: Fix sparse address space warnings
openrisc: uaccess: Add user address space check to access_ok
arch/openrisc/include/asm/io.h | 7 +++++--
arch/openrisc/include/asm/uaccess.h | 21 +++++++++++----------
arch/openrisc/kernel/signal.c | 14 +++++++-------
3 files changed, 23 insertions(+), 19 deletions(-)
--
2.26.2
next reply other threads:[~2020-08-04 4:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-04 4:23 Stafford Horne [this message]
2020-08-04 4:23 ` [PATCH 1/6] openrisc: io: Fixup defines and move include to the end Stafford Horne
2020-08-04 4:23 ` [OpenRISC] " Stafford Horne
2020-08-04 4:23 ` [PATCH 2/6] openrisc: uaccess: Fix sparse address space warnings Stafford Horne
2020-08-04 4:23 ` [OpenRISC] " Stafford Horne
2020-08-04 20:46 ` Luc Van Oostenryck
2020-08-04 20:46 ` [OpenRISC] " Luc Van Oostenryck
2020-08-04 4:23 ` [PATCH 3/6] openrisc: uaccess: Use static inline function in access_ok Stafford Horne
2020-08-04 4:23 ` [OpenRISC] " Stafford Horne
2020-08-04 20:48 ` Luc Van Oostenryck
2020-08-04 20:48 ` [OpenRISC] " Luc Van Oostenryck
2020-08-04 4:23 ` [PATCH 4/6] openrisc: uaccess: Remove unused macro __addr_ok Stafford Horne
2020-08-04 4:23 ` [OpenRISC] " Stafford Horne
2020-08-04 4:23 ` [PATCH 5/6] openrisc: signal: Fix sparse address space warnings Stafford Horne
2020-08-04 4:23 ` [OpenRISC] " Stafford Horne
2020-08-04 4:23 ` [PATCH 6/6] openrisc: uaccess: Add user address space check to access_ok Stafford Horne
2020-08-04 4:23 ` [OpenRISC] " Stafford Horne
2020-08-04 20:50 ` Luc Van Oostenryck
2020-08-04 20:50 ` [OpenRISC] " Luc Van Oostenryck
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=20200804042354.3930694-1-shorne@gmail.com \
--to=shorne@gmail.com \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.