| To: | bpm@xxxxxxx |
|---|---|
| Subject: | Re: [PATCH 2/2] xfs_export_operations.commit_metadata |
| From: | "J. Bruce Fields" <bfields@xxxxxxxxxxxx> |
| Date: | Fri, 12 Feb 2010 15:03:59 -0500 |
| Cc: | Christoph Hellwig <hch@xxxxxxxxxxxxx>, Alex Elder <aelder@xxxxxxx>, linux-nfs@xxxxxxxxxxxxxxx, xfs@xxxxxxxxxxx |
| In-reply-to: | <20100212195647.GQ23654@xxxxxxx> |
| References: | <20100211220454.26466.37578.stgit@case> <20100211220505.26466.99037.stgit@case> <1265986006.3201.112.camel@doink1> <20100212174706.GB22633@xxxxxxxxxxxxx> <20100212195647.GQ23654@xxxxxxx> |
| User-agent: | Mutt/1.5.18 (2008-05-17) |
On Fri, Feb 12, 2010 at 01:56:47PM -0600, bpm@xxxxxxx wrote: > On Fri, Feb 12, 2010 at 12:47:07PM -0500, Christoph Hellwig wrote: > > if we care enough about the returned error. But Ben is working against > > the NFS tree which doesn't have that change yet. > > > > We can deal with that by either commiting the old variant to the nfs > > tree and then leaving sending Stephen a patch to fix it up in -next, > > or just not apply the xfs commit_metadata implementation yet, and wait > > for it until both the xfs and nfs trees have hit mainline. Assuming the xfs tree's something stable, I could also just go ahead and pull it into the nfsd tree. (Or we could do it the other way around--as long as when the merge window opens we try to send the pull requests in the same order.) --b. |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: xfs_repair on a 1.5 TiB image has been hanging for about an hour, now, Richard Hartmann |
|---|---|
| Next by Date: | Re: xfs_repair on a 1.5 TiB image has been hanging for about an hour, now, Eric Sandeen |
| Previous by Thread: | Re: [PATCH 2/2] xfs_export_operations.commit_metadata, bpm |
| Next by Thread: | Re: [PATCH 2/2] xfs_export_operations.commit_metadata, Christoph Hellwig |
| Indexes: | [Date] [Thread] [Top] [All Lists] |