public inbox for linux-next@vger.kernel.org 
 help / color / mirror / Atom feed
From: Stephen Rothwell <sfr@canb•auug.org.au>
To: Dave Chinner <david@fromorbit•com>
Cc: "J. Bruce Fields" <bfields@fieldses•org>,
	xfs-masters@oss•sgi.com, linux-next@vger•kernel.org,
	linux-kernel@vger•kernel.org, Ben Myers <bpm@sgi•com>,
	Christoph Hellwig <hch@infradead•org>
Subject: Re: linux-next: build failure after merge of the nfsd and xfs trees
Date: Wed, 24 Feb 2010 13:43:39 +1100	[thread overview]
Message-ID: <20100224134339.da65a976.sfr@canb.auug.org.au> (raw)
In-Reply-To: <20100224015848.GE16175@discord.disaster>

[-- Attachment #1: Type: text/plain, Size: 673 bytes --]

Hi Dave,

On Wed, 24 Feb 2010 12:58:48 +1100 Dave Chinner <david@fromorbit•com> wrote:
>
> I was waiting for this email to come in. ;)

:-)

> Yes, that is the correct fix. Thanks for that, Stephen. Consider it:
> 
> Reviewed-by: Dave Chinner <david@fromorbit•com>

Thanks for the confirmation.

> Іt would be good if you could keep it as a merge fixup - we don't
> really want to have to pull the -next NFS tree into the XFS tree or vice
> versa until one or the other is upstream....

Yep, no problem (I have a system that does that for me).

-- 
Cheers,
Stephen Rothwell                    sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/

[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]

      reply	other threads:[~2010-02-24  2:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-24  1:36 linux-next: build failure after merge of the nfsd and xfs trees Stephen Rothwell
2010-02-24  1:58 ` Dave Chinner
2010-02-24  2:43   ` Stephen Rothwell [this message]

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=20100224134339.da65a976.sfr@canb.auug.org.au \
    --to=sfr@canb$(echo .)auug.org.au \
    --cc=bfields@fieldses$(echo .)org \
    --cc=bpm@sgi$(echo .)com \
    --cc=david@fromorbit$(echo .)com \
    --cc=hch@infradead$(echo .)org \
    --cc=linux-kernel@vger$(echo .)kernel.org \
    --cc=linux-next@vger$(echo .)kernel.org \
    --cc=xfs-masters@oss$(echo .)sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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