From: KaiGai Kohei <kaigai@ak.jp.nec.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: linux-mtd@lists.infradead.org, joern@wohnheim.fh-wedel.de
Subject: Re: [PATCH] XATTR support on JFFS2 (version. 5)
Date: Sun, 07 May 2006 01:47:46 +0900 [thread overview]
Message-ID: <445CD332.40309@ak.jp.nec.com> (raw)
In-Reply-To: <1146919108.2766.73.camel@pmac.infradead.org>
Thanks for your comments.
> 1. Please don't use typedefs. Just 'struct jffs2_acl_header' instead of
> this:
> typedef struct {
> jint32_t a_version;
> } jffs2_acl_header;
OK, I'll fix it.
> 2. You're adding locks without documenting them in README.Locking.
> Please make sure any new locks (c->xattr_sem) are fully documented.
OK, I'll prepare it.
Please notice me, if storange English expressions are included.
> 3. You have very strange locking behaviour in
> jffs2_garbage_collect_xattr() -- sometimes you return with the lock
> still held, sometimes without. I think it would be best to check
> ic->class within the jffs2_garbage_collect_passs() function instead.
Do you prefer the following style implementation?
I also agree your opinion, if so. I'll fix it.
@ gc.c
if (jffs2_garbage_collect_passs(c, ic)) { /* returns 1, if ic is xdatum or xref */
spin_unlock(&c->erase_completion_lock);
jffs2_garbage_collect_xattr(c, ic); /* ic is xdatum or xref */
goto release_sem;
}
:
> 4. You add a list_head to struct jffs2_inode_cache. That's two pointers
> -- could we get away with only a single pointer instead?
It's probably possible. Please wait for a while, since there is a bit much
points to be fixed.
> How much has your code been tested on SMP machines?
It's not evaluated on SMP machine yet.
(And, I've not prepated SMP evaluation environment yet.)
I hope to make collaboration with MTD people.
> Please let me know if you'd like an account with direct access to the
> jffs2-xattr-2.6.git tree. I can continue to apply patches if you prefer,
> but git is quite easy to use.
I haven't known much about detailed git operations yet. But I'm already
doing basical operations such as pull/push/... in my local environment.
Maybe, here is not significant problem. I'm willing to manage jffs2-xattr-2.6.git
tree. Is it necessary to send you my ssh public key, isn't it?
Thanks,
--
KaiGai Kohei <kaigai@kaigai.gr.jp>
next prev parent reply other threads:[~2006-05-06 16:48 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-06 6:51 [PATCH] XATTR support on JFFS2 (version. 5) KaiGai Kohei
2006-05-06 12:07 ` David Woodhouse
2006-05-06 12:38 ` David Woodhouse
2006-05-06 16:47 ` KaiGai Kohei [this message]
2006-05-06 17:53 ` David Woodhouse
2006-05-07 0:22 ` KaiGai Kohei
2006-05-07 0:29 ` David Woodhouse
2006-05-07 10:19 ` Artem B. Bityutskiy
2006-05-07 13:25 ` Artem B. Bityutskiy
2006-05-07 13:29 ` David Woodhouse
2006-05-07 12:46 ` Artem B. Bityutskiy
2006-05-07 13:12 ` Artem B. Bityutskiy
2006-05-07 13:18 ` David Woodhouse
2006-05-08 1:01 ` KaiGai Kohei
2006-05-07 17:16 ` Jörn Engel
2006-05-08 2:03 ` KaiGai Kohei
2006-05-08 12:49 ` David Woodhouse
2006-05-09 16:10 ` KaiGai Kohei
2006-05-11 23:16 ` KaiGai Kohei
2006-05-11 23:31 ` David Woodhouse
2006-05-12 15:20 ` KaiGai Kohei
2006-05-12 15:32 ` Jörn Engel
2006-05-12 15:38 ` David Woodhouse
2006-05-13 6:37 ` KaiGai Kohei
2006-05-13 10:46 ` David Woodhouse
2006-05-10 13:28 ` Jörn Engel
2006-05-10 10:03 ` Artem B. Bityutskiy
2006-05-10 11:06 ` David Woodhouse
2006-05-10 11:22 ` Artem B. Bityutskiy
2006-05-10 12:03 ` KaiGai Kohei
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=445CD332.40309@ak.jp.nec.com \
--to=kaigai@ak.jp.nec.com \
--cc=dwmw2@infradead.org \
--cc=joern@wohnheim.fh-wedel.de \
--cc=linux-mtd@lists.infradead.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