public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: "Justin P. Mattock" <justinmattock@gmail.com>
Cc: linux-kernel@vger.kernel.org, akpm@linux-foundation.org, jkosina@suse.cz
Subject: Re: [PATCH]kernel.h Move warning message about using kernel headers for userspace to types.h
Date: Thu, 1 Jul 2010 09:58:46 +0200	[thread overview]
Message-ID: <201007010958.46720.arnd@arndb.de> (raw)
In-Reply-To: <1277935785-6023-1-git-send-email-justinmattock@gmail.com>

On Thursday 01 July 2010 00:09:45 Justin P. Mattock wrote:
> Hopefully correct, as request move the function that checks
> if userspace is using kernel headers, from kernel.h to types.h.
> (Please check.)
> 
>  Signed-off-by: Justin P. Mattock <justinmattock@gmail.com>

Trivial change: The 'Signed-off-by'-line should start at the beginning
of the line, no space in front of it, to make all tools parse
it correctly.

Also, the text above should really be the changelog in the way
that you want it to appear in the git history. The explanatory
text about what has changed can go below the '---' line, together
with the diffstat information. Git only uses text above the line
as a changeset comment.

> --- a/include/linux/types.h
> +++ b/include/linux/types.h
> @@ -179,6 +179,12 @@ typedef __u32 __bitwise __wsum;
>  typedef unsigned __bitwise__ gfp_t;
>  typedef unsigned __bitwise__ fmode_t;
>  
> +#ifndef __EXPORTED_HEADERS__
> +#ifndef __KERNEL__
> +#warning "Attempt to use kernel headers from user space, see http://kernelnewbies.org/KernelHeaders"
> +#endif /* __KERNEL__ */
> +#endif /* __EXPORTED_HEADERS__ */
> +
>  #ifdef CONFIG_PHYS_ADDR_T_64BIT
>  typedef u64 phys_addr_t;

Good: No more linewrap, correct use of quotation marks.
Bad: This is now inside of #ifdef __KERNEL__, so it can never be caught by
the compiler. Even if it looks like a trivial patch, it's a good idea
to test it.

I'd suggest putting the #ifndef __EXPORTED_HEADERS__ into a new #else
path of the last #ifdef __KERNEL__ of this file.

Anyway, thanks for the persistence, I know it's frustrating when a one-line
change goes through half a dozen revisions.

	Arnd

  reply	other threads:[~2010-07-01  7:59 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-30 22:09 [PATCH]kernel.h Move warning message about using kernel headers for userspace to types.h Justin P. Mattock
2010-07-01  7:58 ` Arnd Bergmann [this message]
2010-07-01 13:34   ` Justin P. Mattock
2010-07-01 15:07     ` Arnd Bergmann
2010-07-01 15:57       ` Justin P. Mattock
2010-07-01 17:20       ` Justin P. Mattock
2010-07-01 20:38         ` Arnd Bergmann
2010-07-01 21:31           ` Justin P. Mattock

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=201007010958.46720.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=akpm@linux-foundation.org \
    --cc=jkosina@suse.cz \
    --cc=justinmattock@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox