From: Greg KH <gregkh@suse.de>
To: Marco <firefox82@alice.it>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Tim Bird <tim.bird@am.sony.com>
Subject: Re: [PATCH 00/16 v4] pramfs: persistent and protected RAM filesystem
Date: Mon, 22 Nov 2010 10:27:51 -0800 [thread overview]
Message-ID: <20101122182751.GA26250@suse.de> (raw)
In-Reply-To: <4CEAB264.4040909@alice.it>
On Mon, Nov 22, 2010 at 07:11:48PM +0100, Marco wrote:
> Il 20/11/2010 10:56, Marco Stornelli ha scritto:
> >
> > Andrew/Greg, can you insert the code in the mm/staging tree?
> >
>
> Please, can I have a positive/negative feedback about that? Thanks.
I can add it to the staging tree _if_ the code is under drivers/staging/
which I do not think your patch places the code at, right?
So if you wish to do that, I'd be glad to take it, but you need to have
a list of things left to do to get it integrated into the "main" portion
of the kernel. Do you have that at the moment?
thanks,
greg k-h
prev parent reply other threads:[~2010-11-22 18:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-20 9:56 [PATCH 00/16 v4] pramfs: persistent and protected RAM filesystem Marco Stornelli
2010-11-22 18:11 ` Marco
2010-11-22 18:27 ` Greg KH [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=20101122182751.GA26250@suse.de \
--to=gregkh@suse.de \
--cc=akpm@linux-foundation.org \
--cc=firefox82@alice.it \
--cc=linux-kernel@vger.kernel.org \
--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