From: Christoph Hellwig <hch@infradead.org>
To: Lachlan McIlroy <lachlan@sgi.com>
Cc: sgi.bugs.xfs@engr.sgi.com, xfs@oss.sgi.com
Subject: Re: TAKE 988141 - Fix build error - use VFS_I() to access linux inode from xfs inode
Date: Tue, 14 Oct 2008 22:21:06 -0400 [thread overview]
Message-ID: <20081015022106.GA22939@infradead.org> (raw)
In-Reply-To: <20081015021055.6B76358FA1E9@chook.melbourne.sgi.com>
FYI I sent this patch out first on 22nd of August, and pinged it on 29th
of Semptember..
next prev parent reply other threads:[~2008-10-15 2:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-15 2:10 TAKE 988141 - Fix build error - use VFS_I() to access linux inode from xfs inode Lachlan McIlroy
2008-10-15 2:21 ` Christoph Hellwig [this message]
2008-10-15 3:30 ` Mark Goodwin
2008-10-15 3:10 ` Russell Cattelan
2008-10-15 5:50 ` Mark Goodwin
2008-10-15 3:36 ` Lachlan McIlroy
2008-10-15 2:40 ` Christoph Hellwig
2008-10-15 3:49 ` Lachlan McIlroy
2008-10-15 2:52 ` Christoph Hellwig
[not found] ` <200810151444.06375.jk@ozlabs.org>
[not found] ` <20081021180349.GA542@infradead.org>
[not found] ` <200810220937.04475.jk@ozlabs.org>
2008-10-22 0:55 ` TAKE 988141 - Fix build error - use VFS_I() to access linux?inode " Mark Goodwin
2008-11-11 21:09 ` Jeremy Kerr
2008-11-11 21:36 ` Mark Goodwin
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=20081015022106.GA22939@infradead.org \
--to=hch@infradead.org \
--cc=lachlan@sgi.com \
--cc=sgi.bugs.xfs@engr.sgi.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox