From: Richard Weinberger <richard.weinberger@gmail.com>
To: Amy Parker <enbyamy@gmail.com>
Cc: dsterba@suse.cz, linux-fsdevel <linux-fsdevel@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 0/3] fs/efs: Follow kernel style guide
Date: Fri, 5 Feb 2021 23:37:46 +0100 [thread overview]
Message-ID: <CAFLxGvz0ZnTs1B7v3R+Zefd5BhE9ximFpgKL8zRmGfOdBrsVfw@mail.gmail.com> (raw)
In-Reply-To: <CAE1WUT4az3ZZ8OU2AS2xxi9h1TbW958ivNXr53jinqHK5vuzMg@mail.gmail.com>
On Fri, Feb 5, 2021 at 11:26 PM Amy Parker <enbyamy@gmail.com> wrote:
>
> On Fri, Feb 5, 2021 at 5:1 AM David Sterba <dsterba@suse.cz> wrote:
> >
> > On Thu, Feb 04, 2021 at 08:52:14PM -0800, Amy Parker wrote:
> > > As the EFS driver is old and non-maintained,
> >
> > Is anybody using EFS on current kernels? There's not much point updating
> > it to current coding style, deleting fs/efs is probably the best option.
> >
>
> Wouldn't be surprised if there's a few systems out there that haven't
> migrated at all.
Before ripping it from the kernel source you could do a FUSE port of EFS.
That way old filesystems can still get used on Linux.
--
Thanks,
//richard
next prev parent reply other threads:[~2021-02-06 3:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-05 4:52 [PATCH 0/3] fs/efs: Follow kernel style guide Amy Parker
2021-02-05 4:52 ` [PATCH 1/3] fs/efs: Use correct brace styling for statements Amy Parker
2021-02-05 4:57 ` Chaitanya Kulkarni
2021-02-05 5:00 ` Amy Parker
2021-02-05 5:09 ` Chaitanya Kulkarni
2021-02-05 5:12 ` Amy Parker
2021-02-05 4:52 ` [PATCH 2/3] fs/efs: Correct spacing after C keywords Amy Parker
2021-02-05 4:52 ` [PATCH 3/3] fs/efs: Fix line breakage for " Amy Parker
2021-02-05 13:19 ` [PATCH 0/3] fs/efs: Follow kernel style guide David Sterba
2021-02-05 15:36 ` Amy Parker
2021-02-05 22:37 ` Richard Weinberger [this message]
2021-02-05 22:49 ` Amy Parker
2021-02-08 0:15 ` David Sterba
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=CAFLxGvz0ZnTs1B7v3R+Zefd5BhE9ximFpgKL8zRmGfOdBrsVfw@mail.gmail.com \
--to=richard.weinberger@gmail.com \
--cc=dsterba@suse.cz \
--cc=enbyamy@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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 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).