From: Christoph Hellwig <hch@infradead.org>
To: Christoph Hellwig <hch@lst.de>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] cleanup fid types mess
Date: Mon, 10 Sep 2007 16:09:35 +0100 [thread overview]
Message-ID: <20070910150935.GB16595@infradead.org> (raw)
In-Reply-To: <20070829134612.GA504@lst.de>
On Wed, Aug 29, 2007 at 03:46:12PM +0200, Christoph Hellwig wrote:
> Currently XFs has three different fid types: struct fid, struct xfs_fid
> and struct xfs_fid2 with hte latter two beeing identicaly and the first
> one beeing the same size but an unstructured array with the same size.
>
> This patch consolidates all this to alway uuse struct xfs_fid.
>
> This patch is required for an upcoming patch series from me that revamps
> the nfs exporting code and introduces a Linux-wide struct fid.
>
>
> Note: the patch is ontop of Eric's inode/vnode tracing cleanup.
Any chance review of this one (and Eric's patch) could be sped up a little
as I have things in the queue relying on this one?
prev parent reply other threads:[~2007-09-10 15:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-29 13:46 [PATCH] cleanup fid types mess Christoph Hellwig
2007-09-10 15:09 ` Christoph Hellwig [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=20070910150935.GB16595@infradead.org \
--to=hch@infradead.org \
--cc=hch@lst.de \
--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