From: Alex Elder <aelder@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 09/15] xfs: rewrite XFS_SEND_NAMESP() as a function
Date: Fri, 02 Jul 2010 14:37:46 -0500 [thread overview]
Message-ID: <1278099466.1876.106.camel@doink> (raw)
In-Reply-To: <20100629075855.GB31118@infradead.org>
On Tue, 2010-06-29 at 03:58 -0400, Christoph Hellwig wrote:
> A lot of arguments for the namesp even are always NULL or use
> defaults. You'll make your life a simpler by just removing them.
> This also applies to some of the other dmapi callout, but it's most
> extreme here.
>
I think I actually did that in later patches in the series,
by setting up a set of new interface routines, one per
event type, rather than multiplexing the namespace event
function for lots of other things.
-Alex
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-07-02 19:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-28 22:05 [PATCH 09/15] xfs: rewrite XFS_SEND_NAMESP() as a function Alex Elder
2010-06-29 7:58 ` Christoph Hellwig
2010-07-02 19:37 ` Alex Elder [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=1278099466.1876.106.camel@doink \
--to=aelder@sgi.com \
--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