From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: Borislav Petkov <bbpetkov@yahoo.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [rfc-patch 0/9] Immediate Values for 2.6.24-rc2-git5
Date: Tue, 20 Nov 2007 12:04:10 -0500 [thread overview]
Message-ID: <20071120170410.GC31044@Krystal> (raw)
In-Reply-To: <20071120051232.GA7210@gollum.tnic>
* Borislav Petkov (bbpetkov@yahoo.de) wrote:
> On Mon, Nov 19, 2007 at 10:31:39AM -0500, Mathieu Desnoyers wrote:
> > * Borislav Petkov (bbpetkov@yahoo.de) wrote:
> > > On Fri, Nov 16, 2007 at 03:02:38PM -0500, Mathieu Desnoyers wrote:
> > > Hi,
> > > just a conventions proposal: have you thought of shortening all those
> > > "immediate_foo" prefixes to 'imm_foo', for example? This'll make the
> > > code much more readable, i think.
> > >
> >
> > Hrm, a quick grep in the kernel tree shows me that the imm_* namespace
> > is already quite clobbered (although I do not detect any imm_read or
> > imm_set).
>
> Right, something called "low level driver for the IOMEGA MatchMaker"
> (drivers/scsi/imm.c) has gotten hold of the imm_* prefix already so there might
> be a problem later, probably. Nevertheless, you could use the imm_ prefix or
> choose some other 3-n letter prefix:
>
> immed_* (3 matches)
> imme_* (no matches but dumb)
> imd_* (none!)
> immv_* (none, v like [v]alues), etc.
> ...
>
I'd go for imv_* then, which indeed stands for "IMmediate Values"
> --
> Regards/Gruß,
> Boris.
--
Mathieu Desnoyers
Computer Engineering Ph.D. Student, Ecole Polytechnique de Montreal
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
prev parent reply other threads:[~2007-11-20 17:04 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 20:02 [rfc-patch 0/9] Immediate Values for 2.6.24-rc2-git5 Mathieu Desnoyers
2007-11-16 20:02 ` [rfc-patch 1/9] Immediate Values - Architecture Independent Code Mathieu Desnoyers
2007-11-16 20:02 ` [rfc-patch 2/9] Immediate Values - Kconfig menu in EMBEDDED Mathieu Desnoyers
2007-11-16 20:02 ` [rfc-patch 3/9] Immediate Values - Move Kprobes x86 restore_interrupt to kdebug.h Mathieu Desnoyers
2007-11-16 20:02 ` [rfc-patch 4/9] x86: add <asm/asm.h> Mathieu Desnoyers
2007-11-16 20:02 ` [rfc-patch 5/9] Add __discard section to x86 Mathieu Desnoyers
2007-11-16 20:02 ` [rfc-patch 6/9] Immediate Values - x86 Optimization Mathieu Desnoyers
2007-11-16 20:02 ` [rfc-patch 7/9] Immediate Values - Powerpc Optimization Mathieu Desnoyers
2007-11-16 20:02 ` [rfc-patch 8/9] Immediate Values - Documentation Mathieu Desnoyers
2007-11-16 20:02 ` [rfc-patch 9/9] Scheduler Profiling - Use Immediate Values Mathieu Desnoyers
2007-11-17 12:50 ` [rfc-patch 0/9] Immediate Values for 2.6.24-rc2-git5 Borislav Petkov
2007-11-18 17:15 ` Mathieu Desnoyers
2007-11-19 15:31 ` Mathieu Desnoyers
2007-11-20 5:12 ` Borislav Petkov
2007-11-20 17:04 ` Mathieu Desnoyers [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=20071120170410.GC31044@Krystal \
--to=mathieu.desnoyers@polymtl.ca \
--cc=bbpetkov@yahoo.de \
--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