From: Charles Manning <manningc2@actrix.gen.nz>
To: Jesper Juhl <jj@chaosbits.net>
Cc: Charles Manning <cdhmanning@gmail.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 2/9] Add yaffs allocator, bitmap and attrib source
Date: Mon, 8 Nov 2010 11:42:47 +1300 [thread overview]
Message-ID: <201011081142.48215.manningc2@actrix.gen.nz> (raw)
In-Reply-To: <alpine.LNX.2.00.1011042357380.16015@swampdragon.chaosbits.net>
On Friday 05 November 2010 12:01:07 Jesper Juhl wrote:
> On Thu, 4 Nov 2010, cdhmanning@gmail.com wrote:
> [snip]
>
> > +void yaffs_free_raw_obj(struct yaffs_dev *dev, struct yaffs_obj *obj)
> > +{
> > +
> > + struct yaffs_allocator *allocator = dev->allocator;
> > +
> > + if (!allocator)
> > + YBUG();
> > + else {
> > + /* Link into the free list. */
> > + obj->siblings.next = (struct list_head
> > *)(allocator->free_objs); + allocator->free_objs = obj;
> > + allocator->n_free_objects++;
> > + }
> > +}
> > +
> > +void yaffs_deinit_raw_tnodes_and_objs(struct yaffs_dev *dev)
> > +{
> > + if (dev->allocator) {
> > + yaffs_deinit_raw_tnodes(dev);
> > + yaffs_deinit_raw_objs(dev);
> > +
> > + YFREE(dev->allocator);
> > + dev->allocator = NULL;
> > + } else
> > + YBUG();
> > +}
> > +
> > +void yaffs_init_raw_tnodes_and_objs(struct yaffs_dev *dev)
> > +{
> > + struct yaffs_allocator *allocator;
> > +
> > + if (!dev->allocator) {
> > + allocator = YMALLOC(sizeof(struct yaffs_allocator));
> > + if (allocator) {
> > + dev->allocator = allocator;
> > + yaffs_init_raw_tnodes(dev);
> > + yaffs_init_raw_objs(dev);
> > + }
> > + } else
> > + YBUG();
> > +}
>
> Tiny style issue; Documentation/CodingStyle says:
>
> "Do not unnecessarily use braces where a single statement will do.
>
> if (condition)
> action();
>
> This does not apply if one branch of a conditional statement is a single
> statement. Use braces in both branches.
>
> if (condition) {
> do_this();
> do_that();
> } else {
> otherwise();
> }
> "
>
> So, in the above, you should have curly braces around both the 'if' and
> 'else' parts since one of them is more than one statement.
Thanks Jesper
Aargh!! I had the code the right way and changed it! My bad for misreading
the CodingStyle.
I have corrected this for the next patch drop, probably a week out.
-- Charles
next prev parent reply other threads:[~2010-11-07 22:42 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-03 16:53 [PATCH 0/9] Add yaffs2 file system cdhmanning
2010-11-03 16:53 ` [PATCH 1/9] Add yaffs Kconfig and Makefile cdhmanning
2010-11-03 17:46 ` Greg KH
2010-11-03 17:55 ` David Daney
2010-11-03 18:06 ` Greg KH
2010-11-04 20:58 ` Charles Manning
2010-11-04 22:36 ` Greg KH
2010-11-05 0:14 ` Ryan Mallon
2010-11-06 1:50 ` Valdis.Kletnieks
2010-11-07 20:59 ` Charles Manning
2010-11-07 21:45 ` Chris Snook
2010-11-07 22:22 ` Charles Manning
2010-11-08 10:24 ` Chris Snook
2010-11-08 21:22 ` Charles Manning
2010-11-08 22:15 ` Chris Snook
2010-11-03 16:53 ` [PATCH 2/9] Add yaffs allocator, bitmap and attrib source cdhmanning
2010-11-04 23:01 ` Jesper Juhl
2010-11-07 22:42 ` Charles Manning [this message]
2010-11-03 16:53 ` [PATCH 3/9] Add yaffs checkpointing, blockinfo, nameval and os context cdhmanning
2010-11-03 16:53 ` [PATCH 4/9] Add yaffs ecc, mtd access and nand abstraction code cdhmanning
2010-11-03 17:05 ` David Daney
2010-11-03 16:53 ` [PATCH 5/9] Add yaffs_guts.c cdhmanning
2010-11-03 16:53 ` [PATCH 6/9] Add some yaffs include files cdhmanning
2010-11-03 17:10 ` David Daney
2010-11-03 17:16 ` Charles Manning
2010-11-09 17:12 ` Arnd Bergmann
2010-11-03 16:53 ` [PATCH 7/9] Add yaffs tag access code cdhmanning
2010-11-03 17:16 ` David Daney
2010-11-03 17:17 ` Paulo Marques
2010-11-03 16:53 ` [PATCH 8/9] Add yaffs verification and version specific code cdhmanning
2010-11-03 16:53 ` [PATCH 9/9] Add yaffs kernel glue cdhmanning
2010-11-09 16:57 ` Arnd Bergmann
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=201011081142.48215.manningc2@actrix.gen.nz \
--to=manningc2@actrix.gen.nz \
--cc=cdhmanning@gmail.com \
--cc=jj@chaosbits.net \
--cc=linux-fsdevel@vger.kernel.org \
--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
all inboxes | Powered by JetHome®