From: Russell Cattelan <cattelan@thebarn.com>
To: Christoph Hellwig <hch@lst.de>, xfs@oss.sgi.com
Subject: Re: [PATCH 0/2] kill bhv_vnode_t
Date: Wed, 23 Jul 2008 16:53:17 -0500 [thread overview]
Message-ID: <4887A84D.90701@thebarn.com> (raw)
In-Reply-To: <20080723214737.GA10655@lst.de>
Christoph Hellwig wrote:
> Dave complained today that the fate of bhv_vnode_t isn't entirely clear
> yet, so I've prepared these two patches to kill it in a minimally
> invasive way. While it causes churn in a lot of areas it does not
> affect the generated code at all.
>
>
I know a bunch of stuff has gone in that is not very portable, which is
fine since
they can be dealt with individually since they are not that intrusive.
Changing bhv_vnode_t to struct inode throughout the code is a pretty big
change and would be a major pain to work around.
-Russell
next prev parent reply other threads:[~2008-07-23 21:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-23 21:47 [PATCH 0/2] kill bhv_vnode_t Christoph Hellwig
2008-07-23 21:53 ` Russell Cattelan [this message]
2008-07-23 21:57 ` Christoph Hellwig
2008-07-23 23:58 ` Russell Cattelan
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=4887A84D.90701@thebarn.com \
--to=cattelan@thebarn.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.