From: Mark Goodwin <markgw@sgi.com>
To: Jeremy Kerr <jk@ozlabs.org>
Cc: Christoph Hellwig <hch@infradead.org>,
lachlan@sgi.com, Timothy Shimmin <tes@sgi.com>,
xfs-oss <xfs@oss.sgi.com>
Subject: Re: TAKE 988141 - Fix build error - use VFS_I() to access linux?inode from xfs inode
Date: Wed, 12 Nov 2008 08:36:35 +1100 [thread overview]
Message-ID: <4919FAE3.10103@sgi.com> (raw)
In-Reply-To: <200811120809.37983.jk@ozlabs.org>
Jeremy Kerr wrote:
> Hi all,
>
>>> I'm still waiting for someone to reply to my previous request:
>> oh sorry, I missed that request.
>
> Do you guys still want a patchwork setup?
No, we've got patchwork set up on xfs.org for now, thanks anyway :)
Cheers
> If so, I'm still waiting on
> this:
>
>>>> Also, I need the following to set up the patchworks project:
>>>>
>>>> * The List-ID (or X-Mailing-List) header added to list messages
>>>> * The mailing list address.
>>>>
>>>> Alternatively, just forward me a message that's been through the
>>>> list.
>
> Cheers,
>
>
> Jeremy
--
Mark Goodwin markgw@sgi.com
Engineering Manager for XFS and PCP Phone: +61-3-99631937
SGI Australian Software Group Cell: +61-4-18969583
-------------------------------------------------------------
prev parent reply other threads:[~2008-11-11 21:37 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
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 [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=4919FAE3.10103@sgi.com \
--to=markgw@sgi.com \
--cc=hch@infradead.org \
--cc=jk@ozlabs.org \
--cc=lachlan@sgi.com \
--cc=tes@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