From: Eric Sandeen <sandeen@sandeen.net>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: [PATCH] remove flags param from xfs_free_eofblocks
Date: Thu, 01 Jan 2009 17:04:39 -0600 [thread overview]
Message-ID: <495D4C07.5050903@sandeen.net> (raw)
In-Reply-To: <20090101230354.GF7510@infradead.org>
Christoph Hellwig wrote:
> On Thu, Jan 01, 2009 at 05:57:17PM -0500, Christoph Hellwig wrote:
>> On Thu, Jan 01, 2009 at 04:45:31PM -0600, Eric Sandeen wrote:
>>> Remove unused XFS_FREE_EOF_NOLOCK and make XFS_FREE_EOF_LOCK default.
>>>
>>> XFS_FREE_EOF_NOLOCK is never used, so remove it, make
>>> XFS_FREE_EOF_LOCK the only behavior, and remove the
>>> flags parameters.
>> Looks good to me.
>
> Actually it's used by dmapi, so we have to keep it. Would be nice if
> we actually had some uptodate tree with dmapi, though..
>
yep I had the wrong tree :( sorry for the noise.
-Eric
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2009-01-01 23:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-01 22:45 [PATCH] remove flags param from xfs_free_eofblocks Eric Sandeen
2009-01-01 22:57 ` Christoph Hellwig
2009-01-01 23:03 ` Christoph Hellwig
2009-01-01 23:04 ` Eric Sandeen [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=495D4C07.5050903@sandeen.net \
--to=sandeen@sandeen.net \
--cc=hch@infradead.org \
--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