From: Lachlan McIlroy <lachlan@sgi.com>
To: Lachlan McIlroy <lachlan@sgi.com>, xfs@oss.sgi.com, markgw@sgi.com
Subject: Re: TAKE 981498 - Use xfs_idestroy() to cleanup an inode.
Date: Wed, 20 Aug 2008 16:13:22 +1000 [thread overview]
Message-ID: <48ABB602.5030404@sgi.com> (raw)
In-Reply-To: <20080820035642.GB6061@disturbed>
This change was part of another patch that you reviewed. This small
change got left out when I merged my changes in with your inode
allocation cleanup which you asked me to do. I also had to modify
your original patch because it did not apply cleanly due other changes
that you made (the semaphore completion stuff). I didn't have to take
your cleanup patch - I could have just fixed the bug. So in amongst
your complaining I'll assume there is a covert "thanks for taking my
patch".
Dave Chinner wrote:
> On Wed, Aug 20, 2008 at 01:33:02PM +1000, Lachlan McIlroy wrote:
>> Use xfs_idestroy() to cleanup an inode.
>
> I'm not sure what has been checked in this patch, even though it's
> recorded that I reviewed it. Yes, I reviewed the original patch, but
> I asked for changes to be made. I *haven't reviewed* what got
> checked in.
>
> With the changelog being entirely useless - not even mentioning it
> fixes a memory leak or a deadlock - I have no idea what changes were
> made in response to my initial review. I now have to wait for CVS
> or git to be updated before being able to find out what just got
> checked in so I can review it.
>
> Lachlan (and for everyone else @ sgi), in future if someone in the
> community reviews a patch and asks for change, can you please repost
> the modified patches to close the review cycle before anything is
> checked in?
>
> Cheers,
>
> Dave.
next prev parent reply other threads:[~2008-08-20 6:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-20 3:33 TAKE 981498 - Use xfs_idestroy() to cleanup an inode Lachlan McIlroy
2008-08-20 3:56 ` Dave Chinner
2008-08-20 6:13 ` Lachlan McIlroy [this message]
2008-08-20 11:15 ` 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=48ABB602.5030404@sgi.com \
--to=lachlan@sgi.com \
--cc=markgw@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