From: Eric Sandeen <sandeen@sandeen.net>
To: Nathan Scott <nathans@sgi.com>
Cc: dgc@sgi.com, xfs@oss.sgi.com
Subject: Re: [PATCH] kill no-op buf macros
Date: Sun, 30 Jul 2006 19:25:51 -0500 [thread overview]
Message-ID: <44CD4E0F.2070905@sandeen.net> (raw)
In-Reply-To: <20060731090815.B2280998@wobbly.melbourne.sgi.com>
Nathan Scott wrote:
> On Sat, Jul 29, 2006 at 10:41:09PM -0500, Eric Sandeen wrote:
>> It looks like these macros are not particularly interesting... this patch kills
>> them.
>
> Hmm, I'm not sure about some of these..
>
>> #define XFS_BUF_BUSY(bp) do { } while (0)
>> #define XFS_BUF_ISBUSY(bp) (1)
>
> This ones used on 2.4, I'd like to get Daves thoughts on whether
> we do the right thing here based on his buffer cache fu.
Grr, just realized my cvs checkout didn't even pull linux-2.4 :/ Suppose I'd
better re-check everything I sent.
Grr!
-Eric
next prev parent reply other threads:[~2006-07-31 0:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-30 3:41 [PATCH] kill no-op buf macros Eric Sandeen
2006-07-30 23:08 ` Nathan Scott
2006-07-31 0:25 ` Eric Sandeen [this message]
2006-07-31 4:03 ` Eric Sandeen
2006-08-09 1:24 ` David Chinner
2006-08-09 2:43 ` Eric Sandeen
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=44CD4E0F.2070905@sandeen.net \
--to=sandeen@sandeen.net \
--cc=dgc@sgi.com \
--cc=nathans@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox