From: Daniel Axtens <dja@axtens•net>
To: linuxppc-dev@lists•ozlabs.org
Cc: Daniel Axtens <dja@axtens•net>
Subject: [PATCH 0/3] powerpc/sparse: constify addresses in get_user macros
Date: Mon, 30 Jan 2017 17:41:52 +1100 [thread overview]
Message-ID: <20170130064155.30281-1-dja@axtens.net> (raw)
Looking through the sparse warnings, I noticed that we were getting
warnings about dropping const qualifiers in get_user calls. This took
a while to figure out: it turns out that if you pass a const pointer
in, sparse will complain when we drop the const qualifier deep inside
the __get_user_ macros. This simple series fixes that, squashing over
60 warnings.
Daniel Axtens (3):
powerpc/sparse: constify the address pointer in __get_user_check
powerpc/sparse: constify the address pointer in __get_user_nocheck
powerpc/sparse: constify the address pointer in __get_user_nosleep
arch/powerpc/include/asm/uaccess.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
--
2.9.3
next reply other threads:[~2017-01-30 6:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-30 6:41 Daniel Axtens [this message]
2017-01-30 6:41 ` [PATCH 1/3] powerpc/sparse: constify the address pointer in __get_user_check Daniel Axtens
2017-02-02 11:45 ` [1/3] " Michael Ellerman
2017-01-30 6:41 ` [PATCH 2/3] powerpc/sparse: constify the address pointer in __get_user_nocheck Daniel Axtens
2017-01-30 6:41 ` [PATCH 3/3] powerpc/sparse: constify the address pointer in __get_user_nosleep Daniel Axtens
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=20170130064155.30281-1-dja@axtens.net \
--to=dja@axtens$(echo .)net \
--cc=linuxppc-dev@lists$(echo .)ozlabs.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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