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 22:38:58 +0200 [thread overview]
Message-ID: <201007012238.58335.arnd@arndb.de> (raw)
In-Reply-To: <4C2CCE57.40208@gmail.com>
On Thursday 01 July 2010, Justin P. Mattock wrote:
> o.k. I resent an updated version. keep in mind this is a bit confusing
> with the __KERNEL__ being in there multiple times, but with the v2 I'm
> able to see the #warning message with my little program.
Well, it's technically correct, but the #ifndef __KERNEL__ in there
would better get dropped, since you are already in the #else path.
> As for the patch itself hopefully I corrected it's changelog etc..
> lately I've been a bit confused with the whole sighned off thing i.g.
> you suggested the #else so naturally I should add your name with a
> sighned off, but with other patches I was told not to do so due to the
> sighned off procedure/process. I'll re-read the submitting patches again
> to make sure.
You got that part right. The S-o-b only ever gets added by a person
sending a patch for the sending address, so you would not add my
address as S-o-B, though you could add it as Cc:.
When someone picks up your patch and forwards it, that person
will add his/her own S-o-b line below yours and keep you listed
as From.
Arnd
next prev parent reply other threads:[~2010-07-01 20:39 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
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 [this message]
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=201007012238.58335.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