linux-fsdevel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <greg@kroah.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Mike Marshall <hubcap@omnibond.com>,
	Al Viro <viro@zeniv.linux.org.uk>, Christoph Hellwig <hch@lst.de>,
	linux-fsdevel <linux-fsdevel@vger.kernel.org>,
	Andrew Morton <akpm@linux-foundation.org>,
	Stephen Rothwell <sfr@canb.auug.org.au>,
	Boaz Harrosh <ooo@electrozaur.com>
Subject: Re: [GIT PULL] Orangefs (text only resend)
Date: Thu, 3 Sep 2015 15:44:49 -0700	[thread overview]
Message-ID: <20150903224449.GA19846@kroah.com> (raw)
In-Reply-To: <CA+55aFyLFPuEunNb9x65LBiJs63yhgstg57iHkF83EvoxOk+qg@mail.gmail.com>

On Thu, Sep 03, 2015 at 01:22:33PM -0700, Linus Torvalds wrote:
> On Wed, Sep 2, 2015 at 6:28 PM, Linus Torvalds
> <torvalds@linux-foundation.org> wrote:
> >
> >             But I would like to see the people who reviewed it and
> > were involved in making it ready to ship actually stand up and say
> > so..
> 
> [ sound of crickets in the background ]
> 
> Ping? Anybody?
> 
> I'm doing my filesystem merges now, but I think I'll delay this in the
> hope to get more feedback from people.

Sorry for the delay.

I've not reviewed the filesystem side, only the kobject handling and
debugfs portions of the filesystem, and they look sane to me.  Much
nicer than the old procfs interface that the code used to have.  So for
that portion, no objection to me for this to be merged.

As for long-term maintenance, I'm pretty sure that Mike is up for it, and
has the resources to do it, he's been working on this for many years now
already, and I doubt that will stop any time soon.

thanks,

greg k-h

  parent reply	other threads:[~2015-09-03 22:44 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-01 15:42 [GIT PULL] Orangefs (text only resend) Mike Marshall
2015-09-02 23:34 ` Linus Torvalds
2015-09-03  1:13   ` Mike Marshall
2015-09-03  1:28     ` Linus Torvalds
2015-09-03 20:22       ` Linus Torvalds
2015-09-03 22:18         ` Mike Marshall
2015-09-03 22:44         ` Greg Kroah-Hartman [this message]
2015-09-06  6:35   ` Christoph Hellwig
2015-09-06  9:08     ` Al Viro
2015-09-06 14:52       ` Mike Marshall
2015-09-06 15:00         ` Mike Marshall
2015-09-06 20:20         ` Al Viro
2015-09-07  6:37           ` Al Viro
2015-09-07 21:10             ` Mike Marshall
2015-09-07 23:22               ` Al Viro
2015-09-08  0:47                 ` Theodore Ts'o
2015-09-08  2:49                   ` Dave Chinner
2015-09-08 14:48                 ` Christoph Hellwig
2015-09-08 18:21                   ` Mike Marshall
2015-09-09 15:05                     ` Mike Marshall
2015-09-11 21:12                       ` Mike Marshall
2015-09-11 22:24                         ` Al Viro
2015-09-13 11:56                           ` Mike Marshall
2015-09-11 23:20                         ` Linus Torvalds
2015-09-13 11:59                           ` Mike Marshall
2015-09-06 14:35     ` Mike Marshall

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=20150903224449.GA19846@kroah.com \
    --to=greg@kroah.com \
    --cc=akpm@linux-foundation.org \
    --cc=hch@lst.de \
    --cc=hubcap@omnibond.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=ooo@electrozaur.com \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.org \
    --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).