From: Steven Whitehouse <swhiteho@redhat.com>
To: Ingo Molnar <mingo@elte.hu>
Cc: Jan Engelhardt <jengelh@linux01.gwdg.de>,
linux-kernel@vger.kernel.org,
Russell Cattelan <cattelan@redhat.com>,
David Teigland <teigland@redhat.com>,
hch@infradead.org
Subject: Re: [PATCH 07/16] GFS2: Directory handling
Date: Tue, 05 Sep 2006 15:02:03 +0100 [thread overview]
Message-ID: <1157464923.3384.1014.camel@quoit.chygwyn.com> (raw)
In-Reply-To: <20060905084334.GA16788@elte.hu>
On Tue, 2006-09-05 at 10:43 +0200, Ingo Molnar wrote:
> * Steven Whitehouse <swhiteho@redhat.com> wrote:
[some lines snipped]
> > > >+ if ((char *)cur + cur_rec_len >= bh_end) {
> > > >+ if ((char *)cur + cur_rec_len > bh_end) {
> > > >+ gfs2_consist_inode(dip);
> > > >+ return -EIO;
> > > >+ }
> > > >+ return -ENOENT;
> > > >+ }
> > >
> > > if((char *)cur + cur_rec_len > bh_end) {
> > > gfs2_consist_inode(dip);
> > > return -EIO;
> > > } else if((char *)cur + cur_rec_len == bh_end)
> > > return -ENOENT;
> > >
> > ok
>
> this one is not OK! Firstly, Jan, and i mentioned this before, please
> stop using 'if(', it is highly inconsistent and against basic taste. We
> only use this construct for function calls (and macros), not for C
> statements.
I did use use if "if (" form when I made this change rather than a
direct copy & paste from this. So it is ok I think,
Steve.
next prev parent reply other threads:[~2006-09-05 13:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-31 13:34 [PATCH 07/16] GFS2: Directory handling Steven Whitehouse
2006-09-04 11:35 ` Jan Engelhardt
2006-09-05 8:44 ` Steven Whitehouse
2006-09-05 8:43 ` Ingo Molnar
2006-09-05 8:58 ` Andreas Schwab
2006-09-05 10:58 ` Ingo Molnar
2006-09-05 9:22 ` Jan Engelhardt
2006-09-05 11:19 ` Ingo Molnar
2006-09-05 11:22 ` Ingo Molnar
2006-09-05 14:02 ` Steven Whitehouse [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-04-21 16:16 Steven Whitehouse
2006-04-21 16:16 ` Christoph Hellwig
2006-04-24 9:16 ` Steven Whitehouse
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=1157464923.3384.1014.camel@quoit.chygwyn.com \
--to=swhiteho@redhat.com \
--cc=cattelan@redhat.com \
--cc=hch@infradead.org \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=teigland@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.