From: Christoph Hellwig <hch@infradead.org>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 0/3] xfs: More xfs_buf cleanups
Date: Wed, 11 Apr 2012 16:08:22 -0400 [thread overview]
Message-ID: <20120411200821.GK28816@infradead.org> (raw)
In-Reply-To: <1334052213-26870-1-git-send-email-david@fromorbit.com>
On Tue, Apr 10, 2012 at 08:03:30PM +1000, Dave Chinner wrote:
> These 3 patches sit on top of my recent series titled:
>
> [PATCH 0/8] xfs: clean up unit usage in xfs_buf V2
>
> These patches remove bits of the API that are effectively the
> default behaviour used by everything or are redundant. This just
> makes API usage simpler and gives it a smaller footprint to modify
> in future.
If you touch these interfaces any chance you could kill the impliciy
XBF_MAPPED thing we do in various places? Probably best by reversing
it and only pass in an XBF_UNMAPPED for the inode buffers as that's
the only place where we want them.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-04-11 20:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 10:03 [PATCH 0/3] xfs: More xfs_buf cleanups Dave Chinner
2012-04-10 10:03 ` [PATCH 1/3] xfs: kill XBF_LOCK Dave Chinner
2012-04-10 15:00 ` Mark Tinguely
2012-04-10 22:20 ` Dave Chinner
2012-04-11 20:07 ` Christoph Hellwig
2012-04-11 22:51 ` Dave Chinner
2012-04-11 22:59 ` Christoph Hellwig
2012-04-11 23:16 ` Dave Chinner
2012-04-12 13:23 ` Mark Tinguely
2012-04-11 20:05 ` Christoph Hellwig
2012-04-10 10:03 ` [PATCH 2/3] xfs: kill xfs_read_buf() Dave Chinner
2012-04-11 20:06 ` Christoph Hellwig
2012-04-10 10:03 ` [PATCH 3/3] xfs: kill XBF_DONTBLOCK Dave Chinner
2012-04-11 20:06 ` Christoph Hellwig
2012-04-11 20:08 ` Christoph Hellwig [this message]
2012-04-13 12:02 ` [PATCH 0/3] xfs: More xfs_buf cleanups 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=20120411200821.GK28816@infradead.org \
--to=hch@infradead.org \
--cc=david@fromorbit.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