From: Dave Hansen <haveblue@us.ibm.com>
To: Chandra Seetharaman <sekharan@us.ibm.com>
Cc: ckrm-tech@lists.sourceforge.net, linux-mm <linux-mm@kvack.org>
Subject: Re: [ckrm-tech] Re: [PATCH 3/6] CKRM: Add limit support for mem controller
Date: Tue, 05 Apr 2005 12:01:45 -0700 [thread overview]
Message-ID: <1112727705.19430.121.camel@localhost> (raw)
In-Reply-To: <20050405182620.GF32645@chandralinux.beaverton.ibm.com>
On Tue, 2005-04-05 at 11:26 -0700, Chandra Seetharaman wrote:
> On Tue, Apr 05, 2005 at 10:59:02AM -0700, Dave Hansen wrote:
> > On Tue, 2005-04-05 at 10:42 -0700, Chandra Seetharaman wrote:
> > > On Mon, Apr 04, 2005 at 07:10:50AM -0700, Dave Hansen wrote:
> > > > What does "impl" stand for, anyway? implied? implicit? implemented?
> > >
> > > I meant implicit... you can also say implied.... will add in comments to
> > > the dats structure definition.
> >
> > How about changing the name of the structure member? Comments suck.
>
> you mean explicit name like implicit_guarantee ? if comments suck, IMHO,
> impl_guar is good enough an option for a field that holds implicit
> guarantee.
I think you possibly suffer from an a case of ibmersdontlikevowelsitis
which seems to be endemic to our company. In case you're wondering,
Linus already found our missing vowels:
http://www.ussg.iu.edu/hypermail/linux/kernel/0110.1/1294.html
-- Dave
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"aart@kvack.org"> aart@kvack.org </a>
next prev parent reply other threads:[~2005-04-05 19:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-02 3:13 Chandra Seetharaman
2005-04-04 14:10 ` Dave Hansen
2005-04-05 17:42 ` Chandra Seetharaman
2005-04-05 17:59 ` Dave Hansen
2005-04-05 18:26 ` Chandra Seetharaman
2005-04-05 19:01 ` Dave Hansen [this message]
2005-04-05 19:48 ` [ckrm-tech] " Chandra Seetharaman
[not found] ` <1112732985.4200.1973.camel@stark>
2005-04-06 16:48 ` Chandra Seetharaman
2005-04-06 18:35 ` Gerrit Huizenga
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=1112727705.19430.121.camel@localhost \
--to=haveblue@us.ibm.com \
--cc=ckrm-tech@lists.sourceforge.net \
--cc=linux-mm@kvack.org \
--cc=sekharan@us.ibm.com \
/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