All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Austin S. Hemmelgarn" <ahferroin7@gmail.com>
To: Cole <cole@opteqint.net>, linux-kernel@vger.kernel.org
Subject: Re: Variant symlink filesystem
Date: Fri, 11 Mar 2016 11:44:32 -0500	[thread overview]
Message-ID: <56E2F5F0.7040606@gmail.com> (raw)
In-Reply-To: <CACsf_wyTqDyfwVnJeWC3ExO5Jeh5mjKxQP2HmJF6o9wuSXATaA@mail.gmail.com>

On 2016-03-11 11:20, Cole wrote:
> Hi,
>
> I have written a Variant Symlink Filesystem for linux, currently
> implemented as a kernel module:
> https://github.com/onslauth/varsymfs
> The code was written for the 3.x kernel.
>
> I would like to try to get this included into the linux kernel, and am
> willing to hand over all copyright and change the license as needed.
> As such, I would like to know what I can do to try to make this
> happen.
The first two steps for this to happen are making sure it works on newer 
kernels (I haven't looked in-depth at your code, but there are not 
likely to be many changes needed to get it working on 4.4.x assuming you 
have it working already on late 3.x cycle kernels), and then get it 
converted to an in-tree module (this also shouldn't be too difficult 
either, once you figure out which tree to base it on and where to put it 
in the source tree).

Once you get to that point, read through Documentation/SubmittingPatches 
and follow the steps there.  Aside from what's there, you'll probably 
want to include a couple of well described test cases.

  reply	other threads:[~2016-03-11 16:44 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-11 16:20 Variant symlink filesystem Cole
2016-03-11 16:44 ` Austin S. Hemmelgarn [this message]
2016-03-11 20:04 ` Richard Weinberger
2016-03-11 20:15   ` Cole
2016-03-11 20:18     ` Richard Weinberger
2016-03-11 20:22       ` Cole
2016-03-11 20:24         ` Richard Weinberger
2016-03-11 20:32           ` Cole
2016-03-11 20:36             ` Richard Weinberger
2016-03-11 22:27             ` David Lang
2016-03-11 20:38           ` Austin S. Hemmelgarn
2016-03-11 20:52             ` Cole
2016-03-11 21:51               ` Al Viro
2016-03-11 22:03                 ` Cole
2016-03-11 22:24                   ` Al Viro
2016-03-11 22:31                     ` Cole
2016-03-11 22:48                       ` David Lang
2016-03-11 22:54                         ` Cole
2016-03-11 22:38                   ` David Lang

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=56E2F5F0.7040606@gmail.com \
    --to=ahferroin7@gmail.com \
    --cc=cole@opteqint.net \
    --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 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.