From: Greg KH <gregkh@linuxfoundation.org>
To: Anton Altaparmakov <anton@tuxera.com>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>
Subject: Re: Merging backported fscrypt to 4.4?
Date: Thu, 12 Oct 2017 15:45:39 +0200 [thread overview]
Message-ID: <20171012134539.GA29921@kroah.com> (raw)
In-Reply-To: <0C60E331-6397-450B-A6E5-AC42091A1992@tuxera.com>
On Thu, Oct 12, 2017 at 01:26:26PM +0000, Anton Altaparmakov wrote:
> > Anyway, that's a side note, I don't really understand why you need/want
> > fscrypt, if the only in-kernel filesystems that need it, already have
> > this support?
>
> Ah, sorry for not explaining better - we have our own flash friendly
> file system (TFFS), which is not in the tree so we have a vested
> interest in fscrypto being part of the mainline kernel rather than
> maintaining it separately.
Ok, that makes more sense. No, sorry, I'm not going to make changes to
any kernel for an out-of-tree chunk of code. We wouldn't do that in
Linus's latest tree, so of course we wouldn't do it in a stable kernel
tree.
Get your filesystem merged and then we can talk :)
thanks,
greg k-h
next prev parent reply other threads:[~2017-10-12 13:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-12 11:59 Merging backported fscrypt to 4.4? Anton Altaparmakov
2017-10-12 12:11 ` Greg KH
2017-10-12 12:30 ` Anton Altaparmakov
2017-10-12 12:49 ` Greg KH
2017-10-12 13:26 ` Anton Altaparmakov
2017-10-12 13:45 ` Greg KH [this message]
2017-10-12 13:53 ` Anton Altaparmakov
2017-10-12 17:26 ` Willy Tarreau
2017-10-13 8:57 ` Anton Altaparmakov
2017-10-13 14:57 ` Willy Tarreau
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=20171012134539.GA29921@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=anton@tuxera.com \
--cc=stable@vger.kernel.org \
/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.