From: Ryan Mallon <ryan@bluewatersys.com>
To: Jesper Juhl <jj@chaosbits.net>
Cc: Charles Manning <cdhmanning@gmail.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
akpm@linux-foundation.org
Subject: Re: [PATCH 03/10] Add yaffs2 file system: checkpoint streaming
Date: Fri, 11 Feb 2011 11:44:43 +1300 [thread overview]
Message-ID: <4D546A5B.5090301@bluewatersys.com> (raw)
In-Reply-To: <alpine.LNX.2.00.1102102324530.8012@swampdragon.chaosbits.net>
On 02/11/2011 11:27 AM, Jesper Juhl wrote:
> On Wed, 9 Feb 2011, Charles Manning wrote:
>
>> Signed-off-by: Charles Manning <cdhmanning@gmail.com>
>> ---
>> fs/yaffs2/yaffs_checkptrw.c | 408 +++++++++++++++++++++++++++++++++++++++++++
>> fs/yaffs2/yaffs_checkptrw.h | 33 ++++
>> 2 files changed, 441 insertions(+), 0 deletions(-)
>> create mode 100644 fs/yaffs2/yaffs_checkptrw.c
>> create mode 100644 fs/yaffs2/yaffs_checkptrw.h
>>
>> diff --git a/fs/yaffs2/yaffs_checkptrw.c b/fs/yaffs2/yaffs_checkptrw.c
>> new file mode 100644
>> index 0000000..997a618
>> --- /dev/null
>> +++ b/fs/yaffs2/yaffs_checkptrw.c
>> @@ -0,0 +1,408 @@
>> +/*
>> + * YAFFS: Yet Another Flash File System. A NAND-flash specific file system.
>> + *
>> + * Copyright (C) 2002-2011 Aleph One Ltd.
>> + * for Toby Churchill Ltd and Brightstar Engineering
>> + *
>> + * Created by Charles Manning <charles@aleph1.co.uk>
>> + *
>> + * This program is free software; you can redistribute it and/or modify
>> + * it under the terms of the GNU General Public License version 2 as
>> + * published by the Free Software Foundation.
>> + */
>> +
>> +#include "yaffs_checkptrw.h"
>> +#include "yaffs_getblockinfo.h"
>> +
>> +static int yaffs2_checkpt_space_ok(struct yaffs_dev *dev)
>> +{
>> + int blocks_avail = dev->n_erased_blocks - dev->param.n_reserved_blocks;
>> +
>> + yaffs_trace(YAFFS_TRACE_CHECKPOINT,
>> + "checkpt blocks_avail = %d", blocks_avail);
>> +
>> + return (blocks_avail <= 0) ? 0 : 1;
>> +}
>> +
>> +static int yaffs_checkpt_erase(struct yaffs_dev *dev)
>> +{
>> + int i;
>> +
>> + if (!dev->param.erase_fn)
>> + return 0;
>> + yaffs_trace(YAFFS_TRACE_CHECKPOINT,
>> + "checking blocks %d to %d",
>> + dev->internal_start_block, dev->internal_end_block);
>> +
>> + for (i = dev->internal_start_block; i <= dev->internal_end_block; i++) {
>
> Why does 'i' need 'function scope'? can't it just have 'for scope'?
>
> for (int i = dev->internal_start_block; i <= dev->internal_end_block; i++) {
Because we don't do that in kernel code.
ryan@okiwi:linux-2.6$ grep "for (int" * -R | wc -l
16
Those sixteen should be fixed :-). Half of them are in drivers/staging.
~Ryan
--
Bluewater Systems Ltd - ARM Technology Solution Centre
Ryan Mallon 5 Amuri Park, 404 Barbadoes St
ryan@bluewatersys.com PO Box 13 889, Christchurch 8013
http://www.bluewatersys.com New Zealand
Phone: +64 3 3779127 Freecall: Australia 1800 148 751
Fax: +64 3 3779135 USA 1800 261 2934
next prev parent reply other threads:[~2011-02-10 22:44 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-09 3:25 [PATCH 0/10] Add yaffs2 file system: Fifth patchset Charles Manning
2011-02-09 3:25 ` [PATCH 01/10] Add yaffs2 file system: allocators, bitmap and block handling Charles Manning
2011-02-09 3:26 ` [PATCH 02/10] Add yaffs2 file system: attrib and xattrib handling Charles Manning
2011-02-09 22:33 ` Ryan Mallon
2011-02-09 3:26 ` [PATCH 03/10] Add yaffs2 file system: checkpoint streaming Charles Manning
2011-02-10 22:27 ` Jesper Juhl
2011-02-10 22:44 ` Ryan Mallon [this message]
2011-02-10 22:50 ` Charles Manning
2011-02-09 3:26 ` [PATCH 04/10] Add yaffs2 file system: flash interface and ecc handling Charles Manning
2011-02-09 3:26 ` [PATCH 05/10] Add yaffs2 file system: tags handling Charles Manning
2011-02-09 3:26 ` [PATCH 06/10] Add yaffs2 file system: tracing and verification handling Charles Manning
2011-02-11 23:01 ` Ryan Mallon
2011-02-09 3:26 ` [PATCH 07/10] Add yaffs2 file system: yaffs1 and yaffs2 mode handling Charles Manning
2011-02-09 3:26 ` [PATCH 08/10] Add yaffs2 file system: core guts code Charles Manning
2011-02-10 2:27 ` Ryan Mallon
2011-02-09 3:26 ` [PATCH 09/10] Add yaffs2 file system: Linux glue code Charles Manning
2011-02-10 22:07 ` Ryan Mallon
2011-02-10 22:47 ` Charles Manning
2011-02-17 22:24 ` Ryan Mallon
2011-02-09 3:26 ` [PATCH 10/10] Add yaffs2 file system: hok in to Linux tree Charles Manning
2011-02-09 4:52 ` [PATCH 0/10] Add yaffs2 file system: Fifth patchset Christoph Hellwig
2011-02-09 18:22 ` Charles Manning
2011-02-16 8:04 ` Christoph Hellwig
2011-02-16 22:12 ` Charles Manning
2011-02-17 1:48 ` Mark Brown
2011-02-17 2:31 ` Charles Manning
2011-02-17 2:52 ` Ryan Mallon
2011-02-17 3:49 ` Charles Manning
2011-02-17 23:41 ` Greg KH
2011-02-18 0:01 ` Mark Brown
2011-02-18 0:33 ` Greg KH
2011-02-18 0:43 ` Mark Brown
2011-02-18 0:55 ` Ryan Mallon
2011-02-18 0:58 ` Greg KH
2011-02-20 17:25 ` Charles Manning
2011-02-20 20:07 ` Greg KH
2011-02-20 20:52 ` Ryan Mallon
2011-02-20 22:29 ` Greg KH
2011-02-20 22:57 ` Ryan Mallon
2011-02-18 1:08 ` Mark Brown
2011-02-17 3:49 ` Mark Brown
2011-02-17 4:22 ` Charles Manning
2011-02-17 6:08 ` Mark Brown
2011-02-19 17:45 ` Pavel Machek
2011-08-17 12:12 ` Linus Walleij
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=4D546A5B.5090301@bluewatersys.com \
--to=ryan@bluewatersys.com \
--cc=akpm@linux-foundation.org \
--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
Powered by JetHome