From: Jonathan Corbet <corbet@lwn.net>
To: Josh Triplett <josh@joshtriplett.org>
Cc: linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] CodingStyle: Add a chapter on conditional compilation
Date: Mon, 3 Nov 2014 11:46:56 -0500 [thread overview]
Message-ID: <20141103114656.3bf200df@lwn.net> (raw)
In-Reply-To: <430ce084b015d22a597ef7e4f6436dadaea7b23d.1414606455.git.josh@joshtriplett.org>
On Wed, 29 Oct 2014 11:15:17 -0700
Josh Triplett <josh@joshtriplett.org> wrote:
> Document several common practices and conventions regarding conditional
> compilation, most notably the preference for ifdefs in headers rather
> than .c files.
OK, I've picked this one up for my 3.19 docs pull.
Thanks,
jon
next prev parent reply other threads:[~2014-11-03 16:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-29 18:15 [PATCH] CodingStyle: Add a chapter on conditional compilation Josh Triplett
2014-10-29 19:12 ` Geert Uytterhoeven
2014-10-29 22:20 ` Josh Triplett
2014-10-30 0:35 ` Randy Dunlap
2014-10-30 2:24 ` Josh Triplett
2014-10-30 3:33 ` Martin Kelly
2014-11-03 16:46 ` Jonathan Corbet [this message]
2014-11-03 17:47 ` Joe Perches
2014-11-03 18:05 ` Josh Triplett
2014-11-03 18:39 ` Joe Perches
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=20141103114656.3bf200df@lwn.net \
--to=corbet@lwn.net \
--cc=josh@joshtriplett.org \
--cc=linux-doc@vger.kernel.org \
--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 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.