xfs
[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

Re: TAKE 988141 - Fix build error - use VFS_I() to access linux inode fr

from [Mark Goodwin] [Permanent Link][Original]
To: Russell Cattelan <cattelan@xxxxxxxxxxx>
Subject: Re: TAKE 988141 - Fix build error - use VFS_I() to access linux inode from xfs inode
From: Mark Goodwin <markgw@xxxxxxx>
Date: Wed, 15 Oct 2008 15:50:03 +1000
Cc: xfs@xxxxxxxxxxx
In-reply-to: <48F55F17.1020800@thebarn.com>
Organization: SGI Engineering
References: <20081015021055.6B76358FA1E9@chook.melbourne.sgi.com> <20081015022106.GA22939@infradead.org> <48F563E1.4050909@sgi.com> <48F55F17.1020800@thebarn.com>
Reply-to: markgw@xxxxxxx
Sender: xfs-bounce@xxxxxxxxxxx
User-agent: Thunderbird 2.0.0.17 (Windows/20080914)


Russell Cattelan wrote:
Mark Goodwin wrote:


Christoph Hellwig wrote: 
FYI I sent this patch out first on 22nd of August, and pinged it on 29th
of Semptember..


Thus is why we need something like 'patchworks' hooked into the xfs@oss
list - better tracking of patch submissions and their status.
So what is patchworks? 

It's a patch submission tracking system for project mailing lists
such as xfs@oss. See http://ozlabs.org/~jk/projects/patchwork

-- Mark


[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
Previous by Date:  Re: crash with latest code drop., Dave Chinner
Next by Date:  Re: crash with latest code drop., Peter Leckie
Previous by Thread:  Re: TAKE 988141 - Fix build error - use VFS_I() to access linux inode from xfs inode, Russell Cattelan
Next by Thread:  Re: TAKE 988141 - Fix build error - use VFS_I() to access linux inode from xfs inode, Lachlan McIlroy
Indexes:  [Date] [Thread] [Top] [All Lists]