From: David Howells <dhowells@redhat.com>
To: Andrew Morton <akpm@osdl.org>
Cc: David Howells <dhowells@redhat.com>,
torvalds@osdl.org, steved@redhat.com, trond.myklebust@fys.uio.no,
aviro@redhat.com, linux-fsdevel@vger.kernel.org,
linux-cachefs@redhat.com, nfsv4@linux-nfs.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/5] Permit NFS superblock sharing [try #2]
Date: Thu, 02 Mar 2006 17:57:18 +0000 [thread overview]
Message-ID: <13560.1141322238@warthog.cambridge.redhat.com> (raw)
In-Reply-To: <20060302092854.2818e98c.akpm@osdl.org>
Andrew Morton <akpm@osdl.org> wrote:
> Why do you assume that?
Why shouldn't I? If I build my patches against Trond's tree instead of Linus's,
it may still not apply to your -mm tree.
> nfs-apply-mount-root-dentry-override-to-filesystems:
> 3 out of 10 hunks FAILED -- saving rejects to file fs/nfs/inode.c.rej
Would it help you if I split the NFS bits out of patch 2 into a separate patch?
> Ordinarily, yes. But for something like this you should work against the
> NFS development tree, not against mainline.
Okay.
David
next prev parent reply other threads:[~2006-03-02 17:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-01 17:36 [PATCH 0/5] Permit NFS superblock sharing [try #2] David Howells
2006-03-01 17:36 ` [PATCH 1/5] NFS: Permit filesystem to override root dentry on mount " David Howells
2006-03-01 17:36 ` [PATCH 2/5] NFS: Apply mount root dentry override to filesystems " David Howells
2006-03-01 17:36 ` [PATCH 3/5] NFS: Abstract out namespace initialisation " David Howells
2006-03-01 17:36 ` [PATCH 4/5] NFS: Add dentry materialisation op " David Howells
2006-03-01 17:36 ` [PATCH 5/5] NFS: Unify NFS superblocks per-protocol per-server " David Howells
2006-03-02 0:21 ` [PATCH 0/5] Permit NFS superblock sharing " Andrew Morton
2006-03-02 0:21 ` Andrew Morton
2006-03-02 11:04 ` David Howells
2006-03-02 17:31 ` Andrew Morton
2006-03-02 11:45 ` David Howells
2006-03-02 17:28 ` Andrew Morton
2006-03-02 17:57 ` David Howells [this message]
2006-03-02 18:08 ` Andrew Morton
2006-03-02 18:08 ` 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=13560.1141322238@warthog.cambridge.redhat.com \
--to=dhowells@redhat.com \
--cc=akpm@osdl.org \
--cc=aviro@redhat.com \
--cc=linux-cachefs@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nfsv4@linux-nfs.org \
--cc=steved@redhat.com \
--cc=torvalds@osdl.org \
--cc=trond.myklebust@fys.uio.no \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.