public inbox for linux-tegra@vger.kernel.org
 help / color / mirror / Atom feed
From: David Howells <dhowells@redhat.com>
To: Chen Gang <gang.chen@asianux.com>, 'Jiri Kosina' <trivial@kernel.org>
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,
	"dhowells@redhat.com" <dhowells@redhat.com>,
	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-samsun
Subject: Re: [PATCH trivial] include: uapi: standard all files' macro prefix and suffix, excluding "linux/" sub-directory
Date: Mon, 04 Nov 2013 22:03:44 +0000	[thread overview]
Message-ID: <11907.1383602624@warthog.procyon.org.uk> (raw)
In-Reply-To: <51FB6216.6010008@asianux.com>

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.
Userspace sometimes depends on the name in the guard macro:-/

David

  parent reply	other threads:[~2013-11-04 22:03 UTC|newest]

Thread overview: 9+ 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:44 ` Chen Gang
2013-08-02  8:13   ` Eric W. Biederman
2013-08-02  8:31     ` Chen Gang
2013-11-04 22:03 ` David Howells [this message]
2013-11-05  3:34   ` Chen Gang
2013-11-05 11:11     ` David Howells
2013-11-05 12:05       ` Chen Gang
2013-11-07  2:53         ` 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=11907.1383602624@warthog.procyon.org.uk \
    --to=dhowells@redhat.com \
    --cc=airlied@linux.ie \
    --cc=alsa-devel@alsa-project.org \
    --cc=arnd@arndb.de \
    --cc=daniel.vetter@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=fcoe-devel@open-fcoe.org \
    --cc=gang.chen@asianux.com \
    --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=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=trivial@kernel.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox