From: Christoph Hellwig <hch@infradead.org>
To: Alex Elder <aelder@sgi.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 4/5] [PATCH] xfs: simplify buffer to transaction matching
Date: Thu, 29 Apr 2010 09:38:07 -0400 [thread overview]
Message-ID: <20100429133806.GA16259@infradead.org> (raw)
In-Reply-To: <1272548122.3221.77.camel@doink>
On Thu, Apr 29, 2010 at 08:35:22AM -0500, Alex Elder wrote:
> Dave suggested using the xfs_trans_*_item() routines (which maybe
> could be renamed xfs_trans_item_*() someday). That is the right
> thing to do, but not necessary at this point. In fact I prefer
> this smaller change anyway, since it clearly just transforms
> the original xfs_trans_buf_item_match_all() code directly to
> the new result. The switch to use xfs_trans_*_item() can (and
> should) happen as a follow-on patch.
Yes, I'll prepare an incremental patch in the next days.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2010-04-29 13:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-18 0:10 [PATCH 0/5] various cleanups for 2.6.35 Christoph Hellwig
2010-04-18 0:10 ` [PATCH 1/5] xfs: access quotainfo structure directly Christoph Hellwig
2010-04-20 6:28 ` Dave Chinner
2010-04-18 0:10 ` [PATCH 2/5] xfs: remove a few macro indirections in the quota code Christoph Hellwig
2010-04-20 6:31 ` Dave Chinner
2010-04-18 0:10 ` [PATCH 3/5] xfs: removed unused XFS_QMOPT_ flags Christoph Hellwig
2010-04-20 6:33 ` Dave Chinner
2010-04-22 11:49 ` Christoph Hellwig
2010-04-18 0:10 ` [PATCH 4/5] [PATCH] xfs: simplify buffer to transaction matching Christoph Hellwig
2010-04-20 6:41 ` Dave Chinner
2010-05-01 12:58 ` Christoph Hellwig
2010-05-03 4:23 ` Dave Chinner
2010-04-27 14:16 ` Christoph Hellwig
2010-04-29 13:35 ` Alex Elder
2010-04-29 13:38 ` Christoph Hellwig [this message]
2010-04-18 0:10 ` [PATCH 5/5] xfs: remove dead XFS_LOUD_RECOVERY code Christoph Hellwig
2010-04-20 6:44 ` Dave Chinner
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=20100429133806.GA16259@infradead.org \
--to=hch@infradead.org \
--cc=aelder@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 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.