All of lore.kernel.org
 help / color / mirror / Atom feed
From: gang.chen@asianux.com (Chen Gang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arch: arm: uapi: be sure of "_UAPI" prefix for all guard macros
Date: Thu, 14 Nov 2013 10:41:35 +0800	[thread overview]
Message-ID: <5284385F.4030904@asianux.com> (raw)
In-Reply-To: <527C5ECD.8010208@asianux.com>

On 11/08/2013 11:47 AM, Chen Gang wrote:
> For all uapi headers, need use "_UAPI" prefix for its guard macro
> (which will be stripped by "scripts/headers_installer.sh").
> 
> Additional completions:
> 
>  - be sure that all "endif" need be appended related comment, also it
>    has and only has one empty line above and no any lines below either.
> 
>  - be sure that all normal uapi header files need content guard macro.
> 
>  - remove the default "kvm_para.h" which was added in Kbuild.

Oh, sorry, it should use 'generic-y' instead of 'header-y' in Kbuild. I
will send patch v2 for it.

> 
>  - remove the detail address of Free Software Foundation (or can not
>    pass "scripts/checkpatch.pl").
> 

Thanks.
-- 
Chen Gang

WARNING: multiple messages have this Message-ID (diff)
From: Chen Gang <gang.chen@asianux.com>
To: "Will Deacon" <will.deacon@arm.com>,
	"Catalin Marinas" <Catalin.Marinas@arm.com>,
	"Russell King - ARM Linux" <linux@arm.linux.org.uk>,
	"Christoffer Dall" <christoffer.dall@linaro.org>,
	"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
	"Jonathan Austin" <jonathan.austin@arm.com>,
	"Al Viro" <viro@zeniv.linux.org.uk>
Cc: "linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"dhowells@redhat.com" <dhowells@redhat.com>,
	"kvmarm@lists.cs.columbia.edu" <kvmarm@lists.cs.columbia.edu>,
	Hans-Christian Egtvedt <egtvedt@samfundet.no>
Subject: Re: [PATCH] arch: arm: uapi: be sure of "_UAPI" prefix for all guard macros
Date: Thu, 14 Nov 2013 10:41:35 +0800	[thread overview]
Message-ID: <5284385F.4030904@asianux.com> (raw)
In-Reply-To: <527C5ECD.8010208@asianux.com>

On 11/08/2013 11:47 AM, Chen Gang wrote:
> For all uapi headers, need use "_UAPI" prefix for its guard macro
> (which will be stripped by "scripts/headers_installer.sh").
> 
> Additional completions:
> 
>  - be sure that all "endif" need be appended related comment, also it
>    has and only has one empty line above and no any lines below either.
> 
>  - be sure that all normal uapi header files need content guard macro.
> 
>  - remove the default "kvm_para.h" which was added in Kbuild.

Oh, sorry, it should use 'generic-y' instead of 'header-y' in Kbuild. I
will send patch v2 for it.

> 
>  - remove the detail address of Free Software Foundation (or can not
>    pass "scripts/checkpatch.pl").
> 

Thanks.
-- 
Chen Gang

  reply	other threads:[~2013-11-14  2:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-08  3:47 [PATCH] arch: arm: uapi: be sure of "_UAPI" prefix for all guard macros Chen Gang
2013-11-08  3:47 ` Chen Gang
2013-11-14  2:41 ` Chen Gang [this message]
2013-11-14  2:41   ` Chen Gang
2013-11-14  2:42 ` [PATCH v2] " Chen Gang
2013-11-14  2:42   ` Chen Gang
2013-11-14 18:28   ` Christoffer Dall
2013-11-14 18:28     ` Christoffer Dall
2013-11-15  1:33     ` Chen Gang
2013-11-15  1:33       ` Chen Gang

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=5284385F.4030904@asianux.com \
    --to=gang.chen@asianux.com \
    --cc=linux-arm-kernel@lists.infradead.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 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.