All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: bpm@sgi.com
Cc: Christoph Hellwig <hch@infradead.org>,
	Alex Elder <aelder@sgi.com>,
	linux-nfs@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [PATCH 2/2] xfs_export_operations.commit_metadata
Date: Fri, 12 Feb 2010 15:03:59 -0500	[thread overview]
Message-ID: <20100212200359.GA23361@fieldses.org> (raw)
In-Reply-To: <20100212195647.GQ23654@sgi.com>

On Fri, Feb 12, 2010 at 01:56:47PM -0600, bpm@sgi.com 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.

WARNING: multiple messages have this Message-ID (diff)
From: "J. Bruce Fields" <bfields@fieldses.org>
To: bpm@sgi.com
Cc: Christoph Hellwig <hch@infradead.org>,
	linux-nfs@vger.kernel.org, xfs@oss.sgi.com,
	Alex Elder <aelder@sgi.com>
Subject: Re: [PATCH 2/2] xfs_export_operations.commit_metadata
Date: Fri, 12 Feb 2010 15:03:59 -0500	[thread overview]
Message-ID: <20100212200359.GA23361@fieldses.org> (raw)
In-Reply-To: <20100212195647.GQ23654@sgi.com>

On Fri, Feb 12, 2010 at 01:56:47PM -0600, bpm@sgi.com 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.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  reply	other threads:[~2010-02-12 20:03 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-11 22:04 [PATCH 0/2] commit_metadata export operation v4 Ben Myers
2010-02-11 22:04 ` Ben Myers
2010-02-11 22:05 ` [PATCH 1/2] commit_metadata export operation replacing nfsd_sync_dir Ben Myers
2010-02-11 22:05   ` Ben Myers
2010-02-12 14:23   ` Alex Elder
2010-02-12 14:23     ` Alex Elder
2010-02-12 17:31     ` Christoph Hellwig
2010-02-12 17:31       ` Christoph Hellwig
2010-02-11 22:05 ` [PATCH 2/2] xfs_export_operations.commit_metadata Ben Myers
2010-02-11 22:05   ` Ben Myers
2010-02-12 14:46   ` Alex Elder
2010-02-12 14:46     ` Alex Elder
2010-02-12 17:47     ` Christoph Hellwig
2010-02-12 17:47       ` Christoph Hellwig
2010-02-12 19:56       ` bpm
2010-02-12 19:56         ` bpm
2010-02-12 20:03         ` J. Bruce Fields [this message]
2010-02-12 20:03           ` J. Bruce Fields
2010-02-12 20:37           ` Christoph Hellwig
2010-02-12 20:37             ` Christoph Hellwig
2010-02-12 20:35         ` Christoph Hellwig
2010-02-12 20:35           ` Christoph Hellwig
  -- strict thread matches above, loose matches on Subject: below --
2010-02-17 20:05 [PATCH 0/2] commit_metadata export operation v6 Ben Myers
2010-02-17 20:05 ` [PATCH 2/2] xfs_export_operations.commit_metadata Ben Myers
2010-02-17 20:05   ` Ben Myers
2010-02-17 23:05   ` Dave Chinner
2010-02-17 23:05     ` Dave Chinner
2010-02-16 21:04 [PATCH 0/2] commit_metadata export operation v5 Ben Myers
2010-02-16 21:04 ` [PATCH 2/2] xfs_export_operations.commit_metadata Ben Myers
2010-02-16 21:04   ` Ben Myers
2010-02-16 22:07   ` Christoph Hellwig
2010-02-16 22:07     ` Christoph Hellwig
2010-02-17  0:29   ` Dave Chinner
2010-02-17  0:29     ` Dave Chinner
2010-02-11 19:26 [PATCH 0/2] commit_metadata export operation v3 Ben Myers
2010-02-11 19:26 ` [PATCH 2/2] xfs_export_operations.commit_metadata Ben Myers
2010-02-11 19:26   ` Ben Myers

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=20100212200359.GA23361@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=aelder@sgi.com \
    --cc=bpm@sgi.com \
    --cc=hch@infradead.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=xfs@oss.sgi.com \
    /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.