All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chen Gang <gang.chen@asianux.com>
To: David Howells <dhowells@redhat.com>
Cc: xen-devel@lists.xensource.com, jeremy@goop.org, airlied@linux.ie,
	daniel.vetter@ffwll.ch, alsa-devel@alsa-project.org,
	dri-devel@lists.freedesktop.org, perex@perex.cz,
	thierry.reding@gmail.com, linux-mtd@lists.infradead.org,
	sean.hefty@intel.com, virtualization@lists.linux-foundation.org,
	Linux-Arch <linux-arch@vger.kernel.org>,
	"kgene.kim@samsung.com" <kgene.kim@samsung.com>,
	tbergstrom@nvidia.com, jy0922.shim@samsung.com,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	roland@purestorage.com, Takashi Iwai <tiwai@suse.de>,
	Tomi Valkeinen <tomi.valkeinen@ti.com>,
	mtk.manpages@gmail.com, fcoe-devel@open-fcoe.org,
	Paul McKenney <paulmck@linux.vnet.ibm.com>,
	"plagnioj@jcrosoft.com" <plagnioj@jcrosoft.com>,
	Arnd Bergmann <arnd@arndb.de>,
	swarren@wwwdotorg.org, intel-gfx@lists.freedesktop.org,
	inki.dae@samsung.com,
	"linux-samsung-soc@vger.kernel.org" <linux-samsung-soc@vger.k>
Subject: Re: [PATCH trivial] include: uapi: standard all files' macro prefix and suffix, excluding "linux/" sub-directory
Date: Tue, 05 Nov 2013 11:34:26 +0800	[thread overview]
Message-ID: <52786742.1080509@asianux.com> (raw)
In-Reply-To: <11907.1383602624@warthog.procyon.org.uk>

On 11/05/2013 06:03 AM, David Howells wrote:
> Chen Gang <gang.chen@asianux.com> wrote:
> 
>> For "include/uapi/*", excluding "linux/" sub-directory, let all files'
>> macro prefix match the standard format, and give related stand comments
>> for their macro suffix.
>>
>> The related standard format is:
>>
>>   "_SUBDIRNAME_SUBDIRNAME[_SUBDIRNAME]_FILENAME" (1st _SUBDIRNAME is _UAPI), and use '_' instead of '.' and '-'.
> 
> I strongly recommend _against_ this without very careful consideration.

All first-send interface related patches are not for applying, they are
only for discussing.


> Userspace sometimes depends on the name in the guard macro:-/
> 

"the guard macro" is only for prevent itself from being included by
multiple times (an id used by itself -- like a handle), it is not an id
to let other files know about it (it is not a normal using way).

If we really want to check "a file id", normally we will check some
macros which already defined in this header file (or in some scripts,
check file path) instead of checking "its file id"

Using the standard format can be sure of file id is always unique in the
future, and it also can let our interface (Linux's address) more cleaner
and beautiful.


Hmm.. do you mean as an interface, if really have unusual(incorrect)
using ways, we have to bear and compatible with them -- although the
interface never says "it will not be changed in the future".


Thanks.
-- 
Chen Gang

WARNING: multiple messages have this Message-ID (diff)
From: Chen Gang <gang.chen@asianux.com>
To: David Howells <dhowells@redhat.com>
Cc: xen-devel@lists.xensource.com, jeremy@goop.org, airlied@linux.ie,
	daniel.vetter@ffwll.ch, alsa-devel@alsa-project.org,
	dri-devel@lists.freedesktop.org, perex@perex.cz,
	thierry.reding@gmail.com, linux-mtd@lists.infradead.org,
	sean.hefty@intel.com, virtualization@lists.linux-foundation.org,
	Linux-Arch <linux-arch@vger.kernel.org>,
	"kgene.kim@samsung.com" <kgene.kim@samsung.com>,
	tbergstrom@nvidia.com, jy0922.shim@samsung.com,
	Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>,
	roland@purestorage.com, Takashi Iwai <tiwai@suse.de>,
	Tomi Valkeinen <tomi.valkeinen@ti.com>,
	mtk.manpages@gmail.com, fcoe-devel@open-fcoe.org,
	Paul McKenney <paulmck@linux.vnet.ibm.com>,
	"plagnioj@jcrosoft.com" <plagnioj@jcrosoft.com>,
	Arnd Bergmann <arnd@arndb.de>,
	swarren@wwwdotorg.org, intel-gfx@lists.freedesktop.org,
	inki.dae@samsung.com,
	"linux-samsung-soc@vger.kernel.org"
	<linux-samsung-soc@vger.kernel.org>,
	Linux Fbdev development list <linux-fbdev@vger.kernel.org>,
	linux-tegra@vger.kernel.org, davej@redhat.com,
	Thomas Gleixner <tglx@linutronix.de>,
	robert.w.love@intel.com,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	'Jiri Kosina' <trivial@kernel.org>,
	dedekind1@gmail.com, sw0312.kim@samsung.com,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	JBottomley@parallels.com,
	"kyungmin.park@samsung.com" <kyungmin.park@samsung.com>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	dwmw2@infradead.org, David Miller <davem@davemloft.net>,
	shanim@mellanox.com
Subject: Re: [PATCH trivial] include: uapi: standard all files' macro prefix and suffix, excluding "linux/" sub-directory
Date: Tue, 05 Nov 2013 11:34:26 +0800	[thread overview]
Message-ID: <52786742.1080509@asianux.com> (raw)
In-Reply-To: <11907.1383602624@warthog.procyon.org.uk>

On 11/05/2013 06:03 AM, David Howells wrote:
> Chen Gang <gang.chen@asianux.com> wrote:
> 
>> For "include/uapi/*", excluding "linux/" sub-directory, let all files'
>> macro prefix match the standard format, and give related stand comments
>> for their macro suffix.
>>
>> The related standard format is:
>>
>>   "_SUBDIRNAME_SUBDIRNAME[_SUBDIRNAME]_FILENAME" (1st _SUBDIRNAME is _UAPI), and use '_' instead of '.' and '-'.
> 
> I strongly recommend _against_ this without very careful consideration.

All first-send interface related patches are not for applying, they are
only for discussing.


> Userspace sometimes depends on the name in the guard macro:-/
> 

"the guard macro" is only for prevent itself from being included by
multiple times (an id used by itself -- like a handle), it is not an id
to let other files know about it (it is not a normal using way).

If we really want to check "a file id", normally we will check some
macros which already defined in this header file (or in some scripts,
check file path) instead of checking "its file id"

Using the standard format can be sure of file id is always unique in the
future, and it also can let our interface (Linux's address) more cleaner
and beautiful.


Hmm.. do you mean as an interface, if really have unusual(incorrect)
using ways, we have to bear and compatible with them -- although the
interface never says "it will not be changed in the future".


Thanks.
-- 
Chen Gang

WARNING: multiple messages have this Message-ID (diff)
From: gang.chen@asianux.com (Chen Gang)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH trivial] include: uapi: standard all files' macro prefix and suffix, excluding "linux/" sub-directory
Date: Tue, 05 Nov 2013 11:34:26 +0800	[thread overview]
Message-ID: <52786742.1080509@asianux.com> (raw)
In-Reply-To: <11907.1383602624@warthog.procyon.org.uk>

On 11/05/2013 06:03 AM, David Howells wrote:
> Chen Gang <gang.chen@asianux.com> wrote:
> 
>> For "include/uapi/*", excluding "linux/" sub-directory, let all files'
>> macro prefix match the standard format, and give related stand comments
>> for their macro suffix.
>>
>> The related standard format is:
>>
>>   "_SUBDIRNAME_SUBDIRNAME[_SUBDIRNAME]_FILENAME" (1st _SUBDIRNAME is _UAPI), and use '_' instead of '.' and '-'.
> 
> I strongly recommend _against_ this without very careful consideration.

All first-send interface related patches are not for applying, they are
only for discussing.


> Userspace sometimes depends on the name in the guard macro:-/
> 

"the guard macro" is only for prevent itself from being included by
multiple times (an id used by itself -- like a handle), it is not an id
to let other files know about it (it is not a normal using way).

If we really want to check "a file id", normally we will check some
macros which already defined in this header file (or in some scripts,
check file path) instead of checking "its file id"

Using the standard format can be sure of file id is always unique in the
future, and it also can let our interface (Linux's address) more cleaner
and beautiful.


Hmm.. do you mean as an interface, if really have unusual(incorrect)
using ways, we have to bear and compatible with them -- although the
interface never says "it will not be changed in the future".


Thanks.
-- 
Chen Gang

  parent reply	other threads:[~2013-11-05  3:34 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-02  7:39 [PATCH trivial] include: uapi: standard all files' macro prefix and suffix, excluding "linux/" sub-directory Chen Gang
2013-08-02  7:39 ` Chen Gang
2013-08-02  7:39 ` Chen Gang
2013-08-02  7:44 ` Chen Gang
2013-08-02  7:44 ` Chen Gang
2013-08-02  7:44   ` Chen Gang
2013-08-02  7:44   ` Chen Gang
2013-08-02  8:13   ` Eric W. Biederman
2013-08-02  8:13     ` Eric W. Biederman
2013-08-02  8:13     ` Eric W. Biederman
2013-08-02  8:31     ` Chen Gang
2013-08-02  8:31     ` Chen Gang
2013-08-02  8:31       ` Chen Gang
2013-08-02  8:31       ` Chen Gang
2013-11-04 22:03 ` David Howells
2013-11-04 22:03 ` David Howells
2013-11-04 22:03   ` David Howells
2013-11-04 22:03   ` David Howells
2013-11-05  3:34   ` Chen Gang
2013-11-05  3:34   ` Chen Gang [this message]
2013-11-05  3:34     ` Chen Gang
2013-11-05  3:34     ` Chen Gang
2013-11-05 11:11     ` David Howells
2013-11-05 11:11     ` David Howells
2013-11-05 11:11       ` David Howells
2013-11-05 11:11       ` David Howells
2013-11-05 12:05       ` Chen Gang
2013-11-05 12:05         ` Chen Gang
2013-11-05 12:05         ` Chen Gang
2013-11-07  2:53         ` Chen Gang
2013-11-07  2:53         ` Chen Gang
2013-11-07  2:53           ` Chen Gang
2013-11-07  2:53           ` Chen Gang
  -- strict thread matches above, loose matches on Subject: below --
2013-08-02  7:39 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=52786742.1080509@asianux.com \
    --to=gang.chen@asianux.com \
    --cc=airlied@linux.ie \
    --cc=alsa-devel@alsa-project.org \
    --cc=arnd@arndb.de \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dhowells@redhat.com \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=fcoe-devel@open-fcoe.org \
    --cc=inki.dae@samsung.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jeremy@goop.org \
    --cc=jy0922.shim@samsung.com \
    --cc=kgene.kim@samsung.com \
    --cc=konrad.wilk@oracle.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=linux-samsung-soc@vger.k \
    --cc=mtk.manpages@gmail.com \
    --cc=paulmck@linux.vnet.ibm.com \
    --cc=perex@perex.cz \
    --cc=plagnioj@jcrosoft.com \
    --cc=roland@purestorage.com \
    --cc=sean.hefty@intel.com \
    --cc=swarren@wwwdotorg.org \
    --cc=tbergstrom@nvidia.com \
    --cc=thierry.reding@gmail.com \
    --cc=tiwai@suse.de \
    --cc=tomi.valkeinen@ti.com \
    --cc=virtualization@lists.linux-foundation.org \
    --cc=xen-devel@lists.xensource.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.