From: Andi Kleen <ak@muc.de>
To: Martin Schwidefsky <schwidefsky@de.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] s390 (11/12): crypto device driver.
Date: Sat, 09 Oct 2004 11:57:25 +0200 [thread overview]
Message-ID: <m34ql4ciyi.fsf@averell.firstfloor.org> (raw)
In-Reply-To: <2N7vD-4KV-33@gated-at.bofh.it> (Martin Schwidefsky's message of "Fri, 08 Oct 2004 20:20:13 +0200")
Martin Schwidefsky <schwidefsky@de.ibm.com> writes:
> +/**
> + * If we are not using the sparse checker, __user has no use.
> + */
> +#ifdef __CHECKER__
> +# define __user __attribute__((noderef, address_space(1)))
> +#else
> +# define __user
> +#endif
__user should be already defined elsewhere in the kernel.
-Andi
next parent reply other threads:[~2004-10-09 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2N7vD-4KV-33@gated-at.bofh.it>
2004-10-09 9:57 ` Andi Kleen [this message]
2004-10-08 17:41 [PATCH] s390 (11/12): crypto device driver Martin Schwidefsky
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=m34ql4ciyi.fsf@averell.firstfloor.org \
--to=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=schwidefsky@de.ibm.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 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.