From: Lachlan McIlroy <lachlan@sgi.com>
To: Stephen Rothwell <sfr@canb.auug.org.au>
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:05:14 +1100 [thread overview]
Message-ID: <4918E85A.5000701@sgi.com> (raw)
In-Reply-To: <20081107160611.d6f64fdd.sfr@canb.auug.org.au>
Stephen Rothwell wrote:
> Hi all,
>
> On Thu, 6 Nov 2008 10:27:53 -0500 Christoph Hellwig <hch@infradead.org> wrote:
>> On Thu, Nov 06, 2008 at 07:47:54AM +1100, Dave Chinner wrote:
>>>>> I think it's probably the only solution - we need to wait until
>>>>> the I_LOCK bit is cleared from the inode and AFAICT wait_on_inode()
>>>>> is the only way to do it.
>>>> Any resolution?
>>> I was waiting on a comment from Christoph. I'll cc him directly this
>>> time ;)
>> What comment do you expect from me? The fix looks correct, but at some
>> point you should probably run all these exports past Al to get another
>> review. Especially as he's doing major work in this area currently.
>
> OK, I have dropped the xfs tree for today. Let me know when it is sorted
> out.
Okay, your fix is in and it is building again.
next prev parent reply other threads:[~2008-11-11 2:05 UTC|newest]
Thread overview: 8+ 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 [this message]
2008-11-11 2:11 ` 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=4918E85A.5000701@sgi.com \
--to=lachlan@sgi.com \
--cc=david@fromorbit.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=viro@zeniv.linux.org.uk \
--cc=xfs-masters@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).