From: Sam Ravnborg <sam@ravnborg.org>
To: "Michael S. Zick" <lkml@morethan.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [RFC: Style] Kernel coding style for Extended Attributes.
Date: Wed, 3 Jun 2009 21:39:18 +0200 [thread overview]
Message-ID: <20090603193918.GF3100@uranus.ravnborg.org> (raw)
In-Reply-To: <200906031211.49890.lkml@morethan.org>
On Wed, Jun 03, 2009 at 12:11:47PM -0500, Michael S. Zick wrote:
> On Wed June 3 2009, Linus Torvalds wrote:
> >
> > On Wed, 3 Jun 2009, Michael S. Zick wrote:
> > >
> > > Is there a recommended style for the kernel source?
> >
> > I think the recommended style is:
> >
> > "Hide them behind a macro so that they never show up in the source".
> >
>
> That seems to be the general consensus in (/by) practice.
Use __section() to define a section.
See init.h for usage and compiler.h for definition.
Sam
prev parent reply other threads:[~2009-06-03 19:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 15:37 [RFC: Style] Kernel coding style for Extended Attributes Michael S. Zick
2009-06-03 15:45 ` Linus Torvalds
2009-06-03 17:11 ` Michael S. Zick
2009-06-03 19:39 ` Sam Ravnborg [this message]
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=20090603193918.GF3100@uranus.ravnborg.org \
--to=sam@ravnborg.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@morethan.org \
--cc=torvalds@linux-foundation.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