public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: KaiGai Kohei <kaigai@ak.jp.nec.com>
Cc: jmorris@redhat.com, sds@tycho.nsa.gov, russell@coker.com.au,
	lorenzo@gnu.org, linux-mtd@lists.infradead.org,
	"Jörn Engel" <joern@wohnheim.fh-wedel.de>
Subject: Re: [PATCH] XATTR support on JFFS2 (version. 5)
Date: Mon, 08 May 2006 13:49:27 +0100	[thread overview]
Message-ID: <1147092567.2766.146.camel@pmac.infradead.org> (raw)
In-Reply-To: <445EA6D4.5000909@ak.jp.nec.com>

On Mon, 2006-05-08 at 11:03 +0900, KaiGai Kohei wrote:
> [Current TODO list]
> * Fix the declaration of jffs2_acl_header and so on by using 'struct'
>    instead of 'typedef' in kernel space.
> - Fix the declaration of jffs2_acl_header and so on by using 'struct'
>    instead of 'typedef' in user space header.
> * Add documentation about xattr_sem into README.Locking.
> * Call jffs2_garbage_collect_xattr_datum/ref() from gc.c directly
>    instead of jffs2_garbage_collect_xattr()
> - Use unidirection list beween inode_chache and xattr_ref, instead of
>    list_head.
> - Add '#include <linux/list.h>' into xattr.h.
> - Unify each file header part with any jffs2 files.
> - Remove a senseless comment. ("/* forward refence */")
> - Remove unneccesary pointer casts.
> - Remove unneccesary '#ifdef __KERNEL__' on acl.h
> 
> *: It has already prepared, but I've not publicated yet.
> -: It has not prepated yet. I should work from now. 

That's an excellent summary; thanks. It does serve to show that we've
mostly picked on cosmetic details so far though :)

If you have patches committed into a git tree, you should be able to
just 'git-push ssh://git.infradead.org/home/git/jffs2-xattr-2.6.git' to
make it available.

-- 
dwmw2

  reply	other threads:[~2006-05-08 12:49 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
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 [this message]
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=1147092567.2766.146.camel@pmac.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=jmorris@redhat.com \
    --cc=joern@wohnheim.fh-wedel.de \
    --cc=kaigai@ak.jp.nec.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=lorenzo@gnu.org \
    --cc=russell@coker.com.au \
    --cc=sds@tycho.nsa.gov \
    /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