public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@yandex.ru>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Artem.Bityutskiy@nokia.com,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: can UBIFS be taken to linux-next?
Date: Wed, 28 May 2008 08:03:38 +0300	[thread overview]
Message-ID: <483CE7AA.2040304@yandex.ru> (raw)
In-Reply-To: <20080527192942.f4e3dd7b.akpm@linux-foundation.org>

Andrew Morton wrote:
> I'm not aware of any issues which would block a 2.6.27 merge.
> 
> I haven't reviewed the filesystem myself.  Christoph Hellwig seems to
> have had a good go through it and had numerous review comments, but it
> is unclear what stage things are at with addressing them?

Indeed Christoph made a good go through and we appreciate this. We have
addressed most of his requests. I'll just cite the latest UBIFS submit
mail (http://marc.info/?l=linux-kernel&m=121180458401234&w=2):

* Requests from Christoph Hellwig's review (may be found here:
  http://marc.info/?l=linux-kernel&m=121093446502796&w=2). Few things
  related to the background thread were not done though. Here are
  explanations why: http://marc.info/?l=linux-kernel&m=121155640026661&w=2
  and http://marc.info/?l=linux-kernel&m=121119680522445&w=2 (see end
  of the mail).
  Also, we have not changed readdir() implementation so far, but just
  put a comment that we cannot support NFS at the moment. However, we
  have an idea how to fix this, but need some comments from the community.
  We'll send a separate mail describing the problem and the possible
  solution shortly. Nevertheless, this should not be a blocker.

We are currently working on "state-less" (in Christoph's terminology)
readdir() implementation. Here is what we are doing:
http://marc.info/?l=linux-kernel&m=121181030711128&w=2

Would be nice to get some comments on 2 possible issues which will
be present in the new implementation.

-- 
Best Regards,
Artem Bityutskiy (Артём Битюцкий)

  reply	other threads:[~2008-05-28  5:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-27  6:18 can UBIFS be taken to linux-next? Artem Bityutskiy
2008-05-28  1:41 ` Stephen Rothwell
2008-05-28  2:29   ` Andrew Morton
2008-05-28  5:03     ` Artem Bityutskiy [this message]
2008-05-28  5:14   ` Artem Bityutskiy

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=483CE7AA.2040304@yandex.ru \
    --to=dedekind@yandex.ru \
    --cc=Artem.Bityutskiy@nokia.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    /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