public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: KaiGai Kohei <kaigai@kaigai.gr.jp>
To: David Woodhouse <dwmw2@infradead.org>
Cc: joern@wohnheim.fh-wedel.de, linux-mtd@lists.infradead.org,
	KaiGai Kohei <kaigai@ak.jp.nec.com>
Subject: Re: [PATCH] XATTR support on JFFS2 (version. 5)
Date: Sun, 07 May 2006 09:22:38 +0900	[thread overview]
Message-ID: <445D3DCE.2000208@kaigai.gr.jp> (raw)
In-Reply-To: <1146937993.2503.93.camel@shinybook.infradead.org>

Hello,

David Woodhouse wrote:
> I don't like that very much either, to be honest. How about getting rid
> of jffs2_garbage_collect_xattr() altogether, and using this in gc.c
> instead...
> 
> #ifdef CONFIG_JFFS2_FS_XATTR
> 	/* When 'ic' refers xattr_datum/xattr_ref, this node is GCed as xattr.
> 	   We can decide whether this node is inode or xattr by ic->class. */
> 	if (ic->class == RAWNODE_CLASS_XATTR_DATUM ||
> 	    ic->class == RAWNODE_CLASS_XATTR_REF) {
> 		spin_unlock(&c->erase_completion_lock);
> 	/* XXXXXX? */
> 		down_write(&c->xattr_sem);
> 		if (ic->class == RAWNODE_CLASS_XATTR_DATUM)
> 			ret = jffs2_garbage_collect_xattr_datum(c, (void *)ic);
> 		else
> 			ret = jffs2_garbage_collect_xattr_ref(c, (void *)ic);
> 		up_write(&c->xattr_sem);
> 		goto release_sem;
> 	}
> #endif

OK, I'll fix according to your suggestion.
Only one point, I think xattr_sem should be modified in xattr.c for readability.

>>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?
> 
> 
> Yes, please. I'll add an account for you.

I'll send it to you directly.

Thanks,
-- 
KaiGai Kohei <kaigai@ak.jp.nec.com>

  reply	other threads:[~2006-05-07  0:23 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
2006-05-06 17:53       ` David Woodhouse
2006-05-07  0:22         ` KaiGai Kohei [this message]
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=445D3DCE.2000208@kaigai.gr.jp \
    --to=kaigai@kaigai.gr.jp \
    --cc=dwmw2@infradead.org \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=kaigai@ak.jp.nec.com \
    --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