From: David Teigland <teigland@redhat.com>
To: Jesper Juhl <juhl-lkml@dif.dk>
Cc: linux-kernel@vger.kernel.org, akpm@osdl.org
Subject: Re: [PATCH 1a/7] dlm: core locking
Date: Tue, 26 Apr 2005 16:43:18 +0800 [thread overview]
Message-ID: <20050426084318.GG12096@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0504252242510.2941@dragon.hyggekrogen.localhost>
On Mon, Apr 25, 2005 at 11:17:57PM +0200, Jesper Juhl wrote:
> |----- Why the parenthesis?
> ^^^^^--- more parens.
> ^^^^^--- yet more.
> what's your facination with parenthesis?
> ^--- here we go again.
> ^--- and again.
> a few cases of pointless parenthesis around define values...
> Here, again, we have a lot of pointless parenthesis around the values.
> I'm not going to bother pointing out the remaining ones.
Hm, you might have removed some remaining doubt about my paren usage.
Anyway, they're all gone now.
> > + int sb_status;
> > + uint32_t sb_lkid;
> > + char sb_flags;
> > + char * sb_lvbptr;
> why not char *sb_lvbptr; ???
I personally think the right column looks nicer when it's lined up, but a
quick survey shows I'm in the minority, so I'd better get with the
program...
> > +static int dlm_astd(void *data)
> Always returning 0 - why not a void function then?
> > +int dlm_scand(void *data)
> void func?
I think kthread_run() demands this.
Dave
next prev parent reply other threads:[~2005-04-26 8:39 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-25 16:57 [PATCH 1a/7] dlm: core locking David Teigland
2005-04-25 17:40 ` Nish Aravamudan
2005-04-25 21:17 ` Jesper Juhl
2005-04-26 5:10 ` Daniel Phillips
2005-04-26 8:43 ` David Teigland [this message]
2005-04-25 22:46 ` Pavel Machek
2005-04-27 14:48 ` Paul Jackson
2005-04-27 21:41 ` Mark Fasheh
2005-04-28 2:41 ` Daniel Phillips
2005-04-28 12:21 ` Lars Marowsky-Bree
2005-04-29 8:05 ` Daniel Phillips
2005-04-28 3:45 ` David Teigland
2005-04-28 13:48 ` Stephen C. Tweedie
2005-04-28 17:19 ` Joel Becker
2005-04-29 8:10 ` Daniel Phillips
2005-04-29 21:52 ` Mark Fasheh
2005-04-30 0:50 ` Daniel Phillips
2005-04-28 19:21 ` Mark Fasheh
2005-04-29 5:56 ` David Teigland
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=20050426084318.GG12096@redhat.com \
--to=teigland@redhat.com \
--cc=akpm@osdl.org \
--cc=juhl-lkml@dif.dk \
--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