From: Eric B Munson <emunson@mgebm.net>
To: Christoph Lameter <cl@linux.com>
Cc: akpm@linux-foundation.org, linux-mm@kvack.org, mel@csn.ul.ie,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Rename struct task variables from p to tsk
Date: Wed, 12 Jan 2011 13:16:02 -0700 [thread overview]
Message-ID: <20110112201602.GA25957@mgebm.net> (raw)
In-Reply-To: <alpine.DEB.2.00.1101121205120.3053@router.home>
[-- Attachment #1: Type: text/plain, Size: 270 bytes --]
On Wed, 12 Jan 2011, Christoph Lameter wrote:
>
> Use t instead of p? Its a local variable after all.
>
>
I don't find t any more informative than p. As a newcomer to most of this code
informative variable names, even for local variables, is a huge help.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
next prev parent reply other threads:[~2011-01-12 20:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-12 15:19 Eric B Munson
2011-01-12 18:05 ` Christoph Lameter
2011-01-12 20:16 ` Eric B Munson [this message]
2011-01-12 20:23 ` Christoph Lameter
2011-01-12 20:16 ` David Rientjes
2011-01-12 23:14 ` Minchan Kim
2011-01-13 3:23 ` Huang Shijie
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=20110112201602.GA25957@mgebm.net \
--to=emunson@mgebm.net \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mel@csn.ul.ie \
/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