From: Greg KH <gregkh@linuxfoundation.org>
To: Evgeniy Polyakov <zbr@ioremap.net>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
akpm@linux-foundation.org
Subject: Re: pohmelfs: call for inclusion
Date: Wed, 8 Feb 2012 12:26:12 -0800 [thread overview]
Message-ID: <20120208202612.GA6198@kroah.com> (raw)
In-Reply-To: <20120208201254.GD22215@ioremap.net>
On Wed, Feb 08, 2012 at 11:12:54PM +0300, Evgeniy Polyakov wrote:
> On Wed, Feb 08, 2012 at 12:10:08PM -0800, Greg KH (gregkh@linuxfoundation.org) wrote:
> > > But that's enough for advertisement. Here is the code.
> > > I do not know whether it is a good idea to ask it for inclusion into
> > > mainline tree right now skipping drivers/staging part. But anyway, I
> > > post patch to remove drivers/staging/pohmelfs and add fs/pohmelfs
> > > If it is not the way to go, I will resubmit.
> >
> > It would be easiest to just send a patch deleting the old
> > drivers/staging/pohmelfs, or just ask me to do it, which I can, and then
> > send a new patch just with the new code, as it is so different.
>
> pohmelfs-staging-remove.diff does hust that - it removes
> drivers/staging/pohmelfs
> pohmelfs.diff adds new code into fs/pohmelfs
>
> Or did they fail to leak into maillist because of the size?
> If so, they are also accessible via
> http://www.ioremap.net/tmp/pohmelfs.diff (142 Kb)
> http://www.ioremap.net/tmp/pohmelfs-staging-remove.diff (200 Kb)
I need a signed-off-by: for any patch :)
Care to resend me just the remove patch, with the proper changelog and
signed-off-by: so that I can queue it up?
thanks,
greg k-h
next prev parent reply other threads:[~2012-02-08 20:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-08 19:34 pohmelfs: call for inclusion Evgeniy Polyakov
2012-02-08 20:10 ` Greg KH
2012-02-08 20:12 ` Evgeniy Polyakov
2012-02-08 20:26 ` Greg KH [this message]
2012-02-08 20:57 ` Evgeniy Polyakov
2012-02-10 0:54 ` Valdis.Kletnieks
2012-02-10 15:23 ` Evgeniy Polyakov
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=20120208202612.GA6198@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=zbr@ioremap.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.