From: Joel Becker <Joel.Becker@oracle.com>
To: Louis Rilling <louis.rilling@kerlabs.com>
Cc: joel.becker@hawkmoon.kerlabs.com, linux-kernel@vger.kernel.org,
ocfs2-devel@oss.oracle.com
Subject: Re: [BUGFIX][PATCH v2 2/2] configfs: Lock new directory inodes before removing on cleanup after failure
Date: Fri, 11 Jul 2008 13:05:41 -0700 [thread overview]
Message-ID: <20080711200541.GB22577@mail.oracle.com> (raw)
In-Reply-To: <1215183366-17479-3-git-send-email-louis.rilling@kerlabs.com>
On Fri, Jul 04, 2008 at 04:56:06PM +0200, Louis Rilling wrote:
> Changelog:
> - Improve comments and braces as requested by Joel
Also looking good, I want to test them and then send them along.
Joel
--
"When I am working on a problem I never think about beauty. I
only think about how to solve the problem. But when I have finished, if
the solution is not beautiful, I know it is wrong."
- Buckminster Fuller
Joel Becker
Principal Software Developer
Oracle
E-mail: joel.becker@oracle.com
Phone: (650) 506-8127
next prev parent reply other threads:[~2008-07-11 20:06 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-04 14:56 [BUGFIX][PATCH v2 0/2] configfs: Fix cleanup after mkdir() failure Louis Rilling
2008-07-04 14:56 ` [BUGFIX][PATCH v2 1/2] configfs: Prevent userspace from creating new entries under attaching directories Louis Rilling
2008-07-11 20:02 ` Joel Becker
2008-07-04 14:56 ` [BUGFIX][PATCH v2 2/2] configfs: Lock new directory inodes before removing on cleanup after failure Louis Rilling
2008-07-11 20:05 ` Joel Becker [this message]
2008-07-04 16:32 ` [BUGFIX][PATCH v2 0/2] configfs: Fix cleanup after mkdir() failure Louis Rilling
2008-07-06 1:03 ` Joel Becker
2008-07-11 22:07 ` Joel Becker
2008-07-11 22:52 ` Andrew Morton
2008-07-11 23:37 ` Joel Becker
2008-07-16 13:08 ` Louis Rilling
2008-07-16 17:27 ` Joel Becker
2008-07-16 17:56 ` Louis Rilling
2008-07-16 20:43 ` Joel Becker
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=20080711200541.GB22577@mail.oracle.com \
--to=joel.becker@oracle.com \
--cc=joel.becker@hawkmoon.kerlabs.com \
--cc=linux-kernel@vger.kernel.org \
--cc=louis.rilling@kerlabs.com \
--cc=ocfs2-devel@oss.oracle.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