public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Mark Goodwin <markgw@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Lachlan McIlroy <lachlan@sgi.com>,
	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: Wed, 15 Oct 2008 13:30:41 +1000	[thread overview]
Message-ID: <48F563E1.4050909@sgi.com> (raw)
In-Reply-To: <20081015022106.GA22939@infradead.org>



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.

Cheers
-- Mark

  reply	other threads:[~2008-10-15  2:29 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 [this message]
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=48F563E1.4050909@sgi.com \
    --to=markgw@sgi.com \
    --cc=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