linux-api.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nikhilesh Reddy <reddyn@codeaurora.org>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	fuse-devel <fuse-devel@lists.sourceforge.net>,
	linux-kernel@vger.kernel.org, linux-api@vger.kernel.org,
	torvalds@linux-foundation.org, linux-fsdevel@vger.kernel.org,
	viro@zeniv.linux.org.uk, Theodore Ts'o <tytso@mit.edu>,
	jack@suse.cz, Antonio SJ Musumeci <trapexit@spawn.link>,
	sven.utcke@gmx.de, Nikolaus Rath <nikolaus@rath.org>,
	Richard Weinberger <richard@nod.at>
Subject: Re: [PATCH] fuse: Add support for fuse stacked I/O
Date: Thu, 14 Jan 2016 10:57:27 -0800	[thread overview]
Message-ID: <5697EF97.9020800@codeaurora.org> (raw)
In-Reply-To: <20160114045716.GB8006@kroah.com>


>
> Your patch is line-wrapped and impossible to apply.
>
> And why cc: me?  This isn't my area of the kernel...
>
> greg k-h
>

Thanks for trying to apply the patch
and i am extremely  sorry for mangling the lines ( my config was broken)
I cc-ed you and a few other ppl to help with the review and the merge.
I am sorry if i bothered you.
But i would still be grateful for your comments


*I will send out a properly formatted patch shortly.*

To quote Nikolaus Rath
(the current maintainer of fuse userspace[libfuse]) :

[BEGIN QUOTE]
"Officially Miklos is still the maintainer, but I understand he has
almost no time for FUSE at the moment (neither kernel nor userspace). I
have taken over the userspace components, but as far as I know no one
stepped up for the kernel work.

The FUSE kernel components are maintained in the mainline Linux kernel
tree (and have been for quite some time), so nothing is being moved.

The way to get changes into the FUSE kernel module is the same procedure
as for any other kernel code: try to convince a maintainer to commit
your code. This doesn't need to be Miklos. If there's really no
maintainer available to review your patch, you can also try to send it
to Linus directly."
[END QUOTE]

I am hoping for some help from the maintainers to help get the patch 
merged. I have seen a lot of interest on the patch from the fuse 
community and would like to work with the kernel maintainers to help get 
the patch merged into the kernel.

*I will send out a properly formatted patch shortly.* sorry for the bad 
patch
-- 
Thanks
Nikhilesh Reddy

Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project.

  reply	other threads:[~2016-01-14 18:57 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <565394BE.4040506@codeaurora.org>
     [not found] ` <565394BE.4040506-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-01-13 23:53   ` [PATCH] fuse: Add support for fuse stacked I/O Nikhilesh Reddy
2016-01-14  4:57     ` Greg KH
2016-01-14 18:57       ` Nikhilesh Reddy [this message]
     [not found]         ` <5697EF97.9020800-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-01-14 19:19           ` Linus Torvalds
     [not found]             ` <CA+55aFwxaU0Y_UxyKFv6WaYsPWDDzZG-rhVtMuLSPcJ0WLLw2A-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-01-15 16:31               ` Andy Lutomirski
     [not found]                 ` <CALCETrWNQ9ytw1bCOOjFJRstauYc6DocQAmZCF61CErAJ5BF2g-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-01-15 17:37                   ` Antonio SJ Musumeci
     [not found]                     ` <CAB3-ZyT+xcU-0BnNvq-+GsDe6W8=MCWwxguS-+KQ39gajmM5pw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-01-15 17:51                       ` Nikolaus Rath
2016-01-15 19:29                         ` Nikhilesh Reddy
     [not found]                           ` <56994884.9060002-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-01-15 21:38                             ` Nikolaus Rath
2016-01-15 21:43                           ` Linus Torvalds
2016-01-15 21:46                             ` Andy Lutomirski
     [not found]                               ` <CALCETrUA2veiBYYbN1hCSkHxBFyDpe3b=PXg=j53_ZuQBt1FUw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-01-15 21:53                                 ` Linus Torvalds
2016-01-19  2:57                                   ` Nikhilesh Reddy
     [not found]                                     ` <569DA62B.7070701-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-01-20 23:24                                       ` Nikhilesh Reddy
2016-01-15 21:56                           ` [fuse-devel] " Hans Beckerus
     [not found]     ` <5696E366.2080605-sgV2jX0FEOL9JmXXK+q4OQ@public.gmane.org>
2016-01-14  8:25       ` Christoph Hellwig
2016-01-14 15:52         ` Nikolaus Rath
     [not found]           ` <87mvs8qhun.fsf-Zv899e0YUSYPWKMTL/zdXNi2O/JbrIOy@public.gmane.org>
2016-01-15  9:29             ` Christoph Hellwig
2016-01-19  3:07       ` Jann Horn
     [not found]         ` <CAK9i0=ojVmbuDiFXY_sHA12vTWgz9aKwEQuZmmYtUka3zqr=hg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2016-01-20 23:07           ` Nikhilesh Reddy

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=5697EF97.9020800@codeaurora.org \
    --to=reddyn@codeaurora.org \
    --cc=fuse-devel@lists.sourceforge.net \
    --cc=gregkh@linuxfoundation.org \
    --cc=jack@suse.cz \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=nikolaus@rath.org \
    --cc=richard@nod.at \
    --cc=sven.utcke@gmx.de \
    --cc=torvalds@linux-foundation.org \
    --cc=trapexit@spawn.link \
    --cc=tytso@mit.edu \
    --cc=viro@zeniv.linux.org.uk \
    /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).