Re: - disable-ext4.patch removed from -mm tree

Andrew Morton
2008-02-04T20:12:24Z

On Mon, 4 Feb 2008 10:00:44 -0500 Theodore Tso <tytso@mit.edu> wrote:

> On Sun, Feb 03, 2008 at 07:15:40PM -0800, Andrew Morton wrote:
> > On Sun, 3 Feb 2008 20:36:26 -0500 Theodore Tso <tytso@mit.edu> wrote:
> >
> > > On Sun, Feb 03, 2008 at 12:25:51PM -0800, Andrew Morton wrote:
> > > > When I merge David's iget coversion patches this will instead wreck the
> > > > ext4 patchset.
> > >
> > > That's ok, it shouldn't be hard for me to fix this up. How quickly
> > > will you be able to merge David's iget converstion patches?
> >
> > They're about 1,000 patches back.
>
> OK, if you're not planning on pushing David's changes to Linus right
> away, what if I pull in David's
>
> iget-stop-ext4-from-using-iget-and-read_inode-try.patch
>
> and push it plus some other ext4 bug fixes directly to Linus, and let
> you know when that has happened so you can drop David's patch from
> your queue?

Sure, go for it.

> David's changes to ext4 can be applied standalone without the rest of
> his series, so it would be safe to push that to Linus independently
> and in advance of the rest of his series. That should also help
> reduce the number of inter-patch queue dependencies.

That patch series is kind of logjammed anyway because it breaks isofs.
Last time I discussed this with David he seemed to find this amusing rather
than an urgent problem. I'd drop the whole lot if there weren't lots of
other patches dependent upon them. Mayeb I can do a selective droppage,
but I hate going out-of-order, and merging untested patch combinations.