public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: Mingming Cao <cmm@us.ibm.com>
To: Theodore Tso <tytso@mit.edu>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	dhowells@redhat.com,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>
Subject: Re: - disable-ext4.patch removed from -mm tree
Date: Tue, 05 Feb 2008 13:26:43 -0800	[thread overview]
Message-ID: <1202246803.3935.6.camel@localhost.localdomain> (raw)
In-Reply-To: <20080204150044.GK18392@mit.edu>

On Mon, 2008-02-04 at 10:00 -0500, Theodore Tso 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?
> 
> 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.  

I get compile error when builing ext4 patch queue with
iget-stop-ext4-from-using-iget-and-read_inode-try.patch applied, against
2.6.24-git14.

It seems iget-stop-ext4-from-using-iget-and-read_inode-try.patch depends
on patches:  
[PATCH 01/31] Add an ERR_CAST() macro to complement ERR_PTR and co.
[PATCH 03/32] IGET: Introduce a function to register iget failure

Mingming

> That should also help
> reduce the number of inter-patch queue dependencies.
> 
> Regards,
> 
>        	       	      	      	  - Ted
> 
> 
> -
> To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

  parent reply	other threads:[~2008-02-05 21:26 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-03 20:18 - disable-ext4.patch removed from -mm tree akpm
2008-02-03 20:25 ` Andrew Morton
2008-02-04  1:36   ` Theodore Tso
2008-02-04  3:15     ` Andrew Morton
2008-02-04 15:00       ` Theodore Tso
2008-02-04 20:11         ` Andrew Morton
2008-02-04 20:30           ` Theodore Tso
2008-02-05  9:40           ` David Howells
2008-02-05 21:26         ` Mingming Cao [this message]
2008-02-06  1:02           ` Mingming Cao
2008-02-06  1:57             ` Andrew Morton
2008-02-06  2:21               ` Mingming Cao
2008-02-04 20:24       ` merge plans, was " Christoph Hellwig
2008-02-04 22:35         ` Andrew Morton
2008-02-05  9:44           ` Christoph Hellwig
2008-02-05  9:53             ` Andrew Morton

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=1202246803.3935.6.camel@localhost.localdomain \
    --to=cmm@us.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=linux-ext4@vger.kernel.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