From: LEROY Christophe <christophe.leroy@c-s.fr>
To: sparclinux@vger.kernel.org, Mathieu Malaterre <malat@debian.org>
Cc: linux-kernel@vger.kernel.org, linuxppc-dev@lists.ozlabs.org,
Paul Mackerras <paulus@samba.org>,
Michael Ellerman <mpe@ellerman.id.au>
Subject: Re: [PATCH] Remove 'type' argument from access_ok() function
Date: Fri, 04 Jan 2019 18:36:59 +0100 [thread overview]
Message-ID: <20190104183659.Horde.Xco_Q-bqCSSJoWwerf1bVw4@messagerie.si.c-s.fr> (raw)
In-Reply-To: <20190104092758.4378-1-malat@debian.org>
Mathieu Malaterre <malat@debian.org> a écrit :
> In commit 05a4ab823983 ("powerpc/uaccess: fix warning/error with
> access_ok()") an attempt was made to remove a warning by referencing the
> variable `type`, however in commit 96d4f267e40f ("Remove 'type' argument
> from access_ok() function") the variable `type` has been removed.
>
> Revert commit 05a4ab823983 ("powerpc/uaccess: fix warning/error with
> access_ok()") to fix the following compilation error:
>
> arch/powerpc/include/asm/uaccess.h:66:32: error: ‘type’ undeclared
> (first use in this function)
>
> Signed-off-by: Mathieu Malaterre <malat@debian.org>
Should you add a Fixes: 96d4f267e40f ?
Note that sparc arch will have the same issue.
Christophe
> ---
> arch/powerpc/include/asm/uaccess.h | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/powerpc/include/asm/uaccess.h
> b/arch/powerpc/include/asm/uaccess.h
> index b31bf45eebd4..5f0c98e511a0 100644
> --- a/arch/powerpc/include/asm/uaccess.h
> +++ b/arch/powerpc/include/asm/uaccess.h
> @@ -63,7 +63,7 @@ static inline int __access_ok(unsigned long addr,
> unsigned long size,
> #endif
>
> #define access_ok(addr, size) \
> - (__chk_user_ptr(addr), (void)(type), \
> + (__chk_user_ptr(addr), \
> __access_ok((__force unsigned long)(addr), (size), get_fs()))
>
> /*
> --
> 2.19.2
next prev parent reply other threads:[~2019-01-04 17:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-04 9:27 [PATCH] Remove 'type' argument from access_ok() function Mathieu Malaterre
2019-01-04 12:57 ` Michael Ellerman
2019-01-04 17:36 ` LEROY Christophe [this message]
2019-01-04 17:54 ` [PATCH] " Linus Torvalds
2019-01-04 17:42 Guenter Roeck
2019-01-04 18:03 ` Linus Torvalds
2019-01-04 21:52 ` Guenter Roeck
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=20190104183659.Horde.Xco_Q-bqCSSJoWwerf1bVw4@messagerie.si.c-s.fr \
--to=christophe.leroy@c-s.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=malat@debian.org \
--cc=mpe@ellerman.id.au \
--cc=paulus@samba.org \
--cc=sparclinux@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).