public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
	Andreas Dilger <andreas.dilger@intel.com>,
	"Theodore Ts'o" <tytso@mit.edu>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [GIT PULL] ext4 updates for 3.11
Date: Tue, 2 Jul 2013 18:01:11 -0700	[thread overview]
Message-ID: <20130703010111.GA7986@kroah.com> (raw)
In-Reply-To: <CA+55aFxdNVX9koH=GViv1Haj3kU07PD-CTKCNuWrm-c-BF3mQw@mail.gmail.com>

On Tue, Jul 02, 2013 at 05:58:15PM -0700, Linus Torvalds wrote:
> On Tue, Jul 2, 2013 at 5:54 PM, Greg KH <greg@kroah.com> wrote:
> > On Tue, Jul 02, 2013 at 05:02:21PM -0700, Linus Torvalds wrote:
> >>
> >> I'm really not convinced this whole Lustre thing was correctly
> >> handled. Merging it into stable and yet being in such bad shape that
> >> it isn't enabled even there? I just dunno. But I have the turd in my
> >> tree now, let's hope it gets fixed up.
> >
> > It's in "staging", not "stable" :)
> 
> Yes. But what was the reason to actually merge it even there? And once
> it gets merged, disabling it again rather than fixing the problems it
> has?

The problems turned out to be too big, too late in the merge cycle for
me to be able to take them (they still aren't even done, as I don't have
a working set of patches yet.)  So I just disabled it from the build to
give Andreas and team time to get it working properly.

I could have just removed it, but I thought I would give them a chance.

> This is a filesystem that Intel apparently wants to push. I think it
> would have been a better idea to push back a bit and say "at least
> clean it up a bit first". It's not like Intel is one of the clueless
> companies that couldn't have done so and need help from the community.

For this filesystem, it seems that they don't have any resources to do
this work and are relying on the community to help out.  Which is odd,
but big companies are strange some times...

thanks,

greg k-h

  reply	other threads:[~2013-07-03  1:01 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-01 13:55 [GIT PULL] ext4 updates for 3.11 Theodore Ts'o
2013-07-02 17:18 ` Linus Torvalds
2013-07-02 18:04   ` Jan Kara
2013-07-02 23:41     ` Stephen Rothwell
2013-07-03 11:35     ` Theodore Ts'o
2013-07-03 16:09       ` Linus Torvalds
2013-07-02 23:45 ` Stephen Rothwell
2013-07-03  0:02   ` Linus Torvalds
2013-07-03  0:54     ` Greg KH
2013-07-03  0:58       ` Linus Torvalds
2013-07-03  1:01         ` Greg KH [this message]
2013-07-03  3:29           ` Dave Chinner
2013-07-03 18:12             ` Greg KH
2013-07-03 18:40               ` Dilger, Andreas
2013-07-03 23:54                 ` Dave Chinner
2013-07-04  0:28                   ` Greg KH
2018-09-07 13:09             ` Greg KH

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=20130703010111.GA7986@kroah.com \
    --to=greg@kroah.com \
    --cc=andreas.dilger@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sfr@canb.auug.org.au \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    /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