Re: [rfc-patch 0/9] Immediate Values for 2.6.24-rc2-git5

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



* Borislav Petkov ([email protected]) wrote:
> On Mon, Nov 19, 2007 at 10:31:39AM -0500, Mathieu Desnoyers wrote:
> > * Borislav Petkov ([email protected]) 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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]
  Powered by Linux