From: "Martin J. Bligh" <mbligh@aracnet.com>
To: colpatch@us.ibm.com, linux-kernel <linux-kernel@vger.kernel.org>
Cc: Michael Hohnbaum <hohnbaum@us.ibm.com>
Subject: Re: [patch][cleanup] Remove __ from topology macros
Date: Wed, 22 Jan 2003 16:03:55 -0800 [thread overview]
Message-ID: <346410000.1043280235@flay> (raw)
In-Reply-To: <3E2F2DF4.4000507@us.ibm.com>
> When I originally wrote the patches implementing the in-kernel topology macros, they were meant to be called as a second layer of functions, sans underbars. This additional layer was deemed unnecessary and summarily dropped. As such, carrying around (and typing!) all these extra underbars is quite pointless. Here's a patch to nip this in the (sorta) bud. The macros only appear in 16 files so far, most of them being the definitions themselves.
Whee! much cleaner ;-) Very cool.
M.
prev parent reply other threads:[~2003-01-23 0:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-22 23:49 [patch][cleanup] Remove __ from topology macros Matthew Dobson
2003-01-23 0:00 ` William Lee Irwin III
2003-01-23 0:03 ` Martin J. Bligh [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=346410000.1043280235@flay \
--to=mbligh@aracnet.com \
--cc=colpatch@us.ibm.com \
--cc=hohnbaum@us.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