From: Christoph Hellwig <hch@infradead.org>
To: Heiko Carstens <heiko.carstens@de.ibm.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/3] s390: avoid usage of 'new' in header files.
Date: Wed, 1 Feb 2006 18:12:38 +0000 [thread overview]
Message-ID: <20060201181238.GB18464@infradead.org> (raw)
In-Reply-To: <20060201115832.GB9361@osiris.boeblingen.de.ibm.com>
On Wed, Feb 01, 2006 at 12:58:32PM +0100, Heiko Carstens wrote:
> From: Heiko Carstens <heiko.carstens@de.ibm.com>
>
> Don't use 'new' as name for variables, since some C++ sources may include
> these header files.
NACK. Userspace must not include these headers ever, and C++ in the kernel is not
supported.
next prev parent reply other threads:[~2006-02-01 18:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-01 11:58 [PATCH 2/3] s390: avoid usage of 'new' in header files Heiko Carstens
2006-02-01 18:12 ` Christoph Hellwig [this message]
2006-02-02 6:04 ` Heiko Carstens
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=20060201181238.GB18464@infradead.org \
--to=hch@infradead.org \
--cc=akpm@osdl.org \
--cc=heiko.carstens@de.ibm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).