From: Minchan Kim <minchan.kim@gmail.com>
To: Marco Stornelli <marco.stornelli@gmail.com>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
linux-embedded@vger.kernel.org, linux-fsdevel@vger.kernel.org,
Tim Bird <tim.bird@am.sony.com>,
linux-mm@kvack.org
Subject: Re: [PATCH] pramfs: Persistent and protected RAM filesystem
Date: Wed, 6 Oct 2010 09:24:56 +0900 [thread overview]
Message-ID: <AANLkTimbamyq6TnOVmMOjnG2hNWYwsvqBZ2RRvSTXr+X@mail.gmail.com> (raw)
In-Reply-To: <AANLkTik34ZKasZMMpx4wD71k+RPccGLvAi1Cwe5UwZpj@mail.gmail.com>
Hello.
On Tue, Oct 5, 2010 at 8:39 PM, Marco Stornelli
<marco.stornelli@gmail.com> wrote:
> Hi all,
>
> after a lot of improvement, test, bug fix and new features, it's the
> moment for third round with the kernel community to submit PRAMFS for
> mainline. First of all, I have to say thanks to Tim Bird and CELF to
> actively support the project.
Good to know.
Thanks for your endless effort. :)
>
> Since the last review (June 2009) a lot of things are changed:
>
> - removed any reference of BKL
> - fixed the endianess for the fs layout
> - added support for extended attributes, ACLs and security labels
> - moved out any pte manipulations from fs and inserted them in mm
> - implemented the new truncate convention
> - fixed problems with 64bit archs
>
> ...and much more. Complete "story" in the ChangeLog inserted in the
> documentation file.
>
> Since the patch is long, you can download and review the patch from
> the project site: http:\\pramfs.sourceforge.net. The patch version is
> 1.2.1 for kernel 2.6.36.
> In addition, in the web site tech page, you can find a lot of
> information about implementation, technical details, benchemarking and
> so on.
If you really want to merge it, you have to divide patch into
individual patches instead of all-at-once patch.
Individual patches should have a description and clear feature to
review more easily.
And still we need all-at-once patch to apply the patch and test easily.
> Regards,
>
> Marco
>
> --
> To unsubscribe, send a message with 'unsubscribe linux-mm' in
> the body to majordomo@kvack.org. For more info on Linux MM,
> see: http://www.linux-mm.org/ .
> Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
>
>
--
Kind regards,
Minchan Kim
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2010-10-06 0:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-05 11:39 [PATCH] pramfs: Persistent and protected RAM filesystem Marco Stornelli
2010-10-06 0:24 ` Minchan Kim [this message]
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=AANLkTimbamyq6TnOVmMOjnG2hNWYwsvqBZ2RRvSTXr+X@mail.gmail.com \
--to=minchan.kim@gmail.com \
--cc=linux-embedded@vger.kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=marco.stornelli@gmail.com \
--cc=tim.bird@am.sony.com \
/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;
as well as URLs for NNTP newsgroup(s).