From: Stephen Rothwell <sfr@canb•auug.org.au>
To: lachlan@sgi•com
Cc: Dave Chinner <david@fromorbit•com>,
Christoph Hellwig <hch@infradead•org>,
xfs-masters@oss•sgi.com, linux-next@vger•kernel.org,
linux-fsdevel@vger•kernel.org, viro@zeniv•linux.org.uk
Subject: Re: linux-next: xfs tree build failure
Date: Tue, 11 Nov 2008 13:11:09 +1100 [thread overview]
Message-ID: <20081111131109.aa82f37b.sfr@canb.auug.org.au> (raw)
In-Reply-To: <4918E85A.5000701@sgi.com>
[-- Attachment #1: Type: text/plain, Size: 338 bytes --]
Hi Lachlan,
On Tue, 11 Nov 2008 13:05:14 +1100 Lachlan McIlroy <lachlan@sgi•com> wrote:
>
> Okay, your fix is in and it is building again.
Thanks, I saw that this morning, so the xfs tree should be in linux-next
today.
--
Cheers,
Stephen Rothwell sfr@canb•auug.org.au
http://www.canb.auug.org.au/~sfr/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-11-11 2:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 2:23 linux-next: xfs tree build failure Stephen Rothwell
2008-10-30 9:08 ` Dave Chinner
2008-11-05 2:20 ` Stephen Rothwell
2008-11-05 20:47 ` Dave Chinner
2008-11-06 15:27 ` Christoph Hellwig
2008-11-07 5:06 ` Stephen Rothwell
2008-11-11 2:05 ` Lachlan McIlroy
2008-11-11 2:11 ` Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-12-03 23:16 Stephen Rothwell
2008-12-04 5:20 ` Eric Sandeen
2009-03-10 2:45 Stephen Rothwell
2009-03-11 22:52 ` Dave Chinner
2009-03-12 1:04 ` Stephen Rothwell
2009-03-15 12:18 ` Dave Chinner
2009-07-03 0:05 Stephen Rothwell
2009-09-02 1:25 Stephen Rothwell
2009-09-02 1:28 ` Christoph Hellwig
2009-09-02 1:54 ` Felix Blyakher
2009-09-02 2:00 ` Stephen Rothwell
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=20081111131109.aa82f37b.sfr@canb.auug.org.au \
--to=sfr@canb$(echo .)auug.org.au \
--cc=david@fromorbit$(echo .)com \
--cc=hch@infradead$(echo .)org \
--cc=lachlan@sgi$(echo .)com \
--cc=linux-fsdevel@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=viro@zeniv$(echo .)linux.org.uk \
--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