public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David Gibson <david@gibson.dropbear.id.au>
To: Andrew Morton <akpm@osdl.org>
Cc: Miklos Szeredi <miklos@szeredi.hu>,
	torvalds@osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [request for inclusion] Filesystem in Userspace
Date: Thu, 3 Mar 2005 11:20:36 +1100	[thread overview]
Message-ID: <20050303002036.GA22835@localhost.localdomain> (raw)
In-Reply-To: <20050302123123.3d528d05.akpm@osdl.org>

On Wed, Mar 02, 2005 at 12:31:23PM -0800, Andrew Morton wrote:
> Miklos Szeredi <miklos@szeredi.hu> wrote:
> >
> > Do you have any objections to merging FUSE in mainline kernel?
> 
> I was planning on sending FUSE into Linus in a week or two.  That and
> cpusets are the notable features which are 2.6.12 candidates.
> 
> - crashdump seems permanently not-quite-ready
> 
> - perfctr works fine, but is rather deadlocked because it is
>   similar-to-but-different-from ia64's perfmon, and might not be suitable
>   for ppc64 (although things have gone quiet on the latter front).

Not to mention that the ABI is still changing with each release...

> - nfsacl should be OK for 2.6.12 if Trond is OK with it.
> 
> - cachefs is a bit stuck because it's a ton of complex code and afs is
>   the only user of it.  Wiring it up to NFS would help.
> 
> - dm multipath is OK for 2.6.12
> 
> - reiser4 is less clear.  Once all the review comments have been addressed
>   and we start seeing a bit of vendor pull for it, maybe.

-- 
David Gibson			| I'll have my music baroque, and my code
david AT gibson.dropbear.id.au	| minimalist.  NOT _the_ _other_ _way_
				| _around_!
http://www.ozlabs.org/people/dgibson

  parent reply	other threads:[~2005-03-03  0:27 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-02 18:17 [request for inclusion] Filesystem in Userspace Miklos Szeredi
2005-03-02 20:31 ` Andrew Morton
2005-03-02 21:02   ` Marcelo Tosatti
2005-03-03  0:20   ` David Gibson [this message]
2005-03-03  9:14   ` Mikael Pettersson
2005-03-03  9:32     ` Andrew Morton
2005-03-03 15:48       ` Mikael Pettersson
2005-03-03 22:13         ` Andrew Morton
2005-03-03 10:58   ` Anton Altaparmakov
2005-03-06  4:16   ` Kevin P. Fleming
2005-03-02 22:19 ` Christoph Hellwig
2005-03-03  6:41   ` Miklos Szeredi
  -- strict thread matches above, loose matches on Subject: below --
2004-11-15 21:15 [PATCH] [Request " Miklos Szeredi
2004-11-15 22:35 ` Linus Torvalds
2004-11-16  9:08   ` Miklos Szeredi
2004-11-16 10:13     ` Pekka Enberg
2004-11-16 10:20       ` Miklos Szeredi
2004-11-16 11:02         ` Jan Kratochvil
2004-11-16 14:01           ` Miklos Szeredi
2004-11-16 16:33             ` Greg KH
2004-11-17 15:42               ` Miklos Szeredi
2004-11-17 16:57                 ` Nikita Danilov
2004-11-17 17:10                   ` Jan Engelhardt
2004-11-17 17:33                     ` Nikita Danilov
2004-11-17 17:38                       ` Jan Engelhardt
2004-11-17 17:58                         ` Nikita Danilov
2004-11-17 18:09                           ` Jan Engelhardt
2004-11-17 19:58                             ` Mike Waychison

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=20050303002036.GA22835@localhost.localdomain \
    --to=david@gibson.dropbear.id.au \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=torvalds@osdl.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